[BUG]: FYI : Disable "Windows Defender Firewall" service also break Windows Sandbox. about privacy.sexy HOT 4 CLOSED

Hi, great report/contribution thank you. You help many others that could not solve this in #115, #152.

Could you also test if this one (under same category) breaks it too:

Disable "Windows Defender Firewall Authorization Driver" service (breaks Microsoft Store, `netsh advfirewall`, `winget`)

Something like this:

1. Run the script
2. Restart the computer.
3. Verify that it broke or not.
4. Revert changes.
5. Restart the computer.

Your feedback will be valuable and I will update the docs right away. The other script usually breaks the same stuff as the one you figured out.

I cannot test this as I do not have physical windows machine for the moment and I lose connection to my Windows VMs when I disable these.

This may resolve #115 where @CaptainFrosty also mentioned that he disabled some of defender stuff and mentioned that these can be the root cause in #152.

from privacy.sexy.

Hello August Strindberg! 📜

Thank you for your work and especially for your great availability in the « Issues ».

I made an AOMEI’s Backup just before applying the script which allows me to easily revert back for testing purposes.

Below is your request to help you update the documentation.
 

Case A) (driver)

1) Fresh installation without any trace of the script "https://privacy.sexy/"
2) Run the batch with ONLY:

   ➜  Privacy over security
   ➜  ➜ Disable Microsoft Defender
   ➜  ➜  ➜ Disable Microsoft Defender firewall
   ➜  ➜  ➜  ➜ Disable Microsoft Defender Firewall services and drivers
   ➜  ➜  ➜  ➜  ➜ Disable "Windows Defender Firewall Authorization Driver" service (breaks Microsoft Store, netsh advfirewall, winget)

 _(( Note: "$serviceQuery = 'mpsdrv'; ))
 (( "%SYSTEMROOT%\System32\drivers\mpsdrv.sys" ))_

3) Restart the computer.
4) Windows Sandbox is eternally stuck on the big blue icon of its splash screen.
5) Apply the batch from step 2 in "revert" mode.
6) Restart the computer.
7) Windows Sandbox is repaired and works (although a bit slow to start for my taste).
 
 
I AOMEI restore to reset the machine to its state before applying any script « https ://privacy. Sexy/».
 
 
Case B) (service)

1) Fresh installation without any trace of the script "https://privacy.sexy/"
2) Run the batch with ONLY:

   ➜  Privacy over security
   ➜  ➜ Disable Microsoft Defender
   ➜  ➜  ➜ Disable Microsoft Defender firewall
   ➜  ➜  ➜  ➜ Disable Microsoft Defender Firewall services and drivers
   ➜  ➜  ➜  ➜  ➜ Disable "Windows Defender Firewall" service (breaks Microsoft Store, netsh advfirewall, winget)

 _(( Note: "$serviceQuery = 'MpsSvc'; ))
 (( "%WINDIR%\System32\mpssvc.dll" ))_

3) Restart the computer.
4) Windows Sandbox is eternally stuck on the big blue icon of its splash screen.
5) Apply the batch from step 2 in "revert" mode.
6) Restart the computer.
7) Windows Sandbox is repaired and works (although a bit slow to start for my taste).

Conclusion:

Whether we remove only the Drivers or the service, in both cases it breaks Windows Sandbox. Obviously, if we apply both at the same time, it's not any better.

I want to specify that in both cases, the script in « revert » mode repairs Windows Sandbox but ONLY AFTER restarting Windows.

So, by analogy and based on tests in reality: if we apply both scripts that break Windows Sandbox and then apply both scripts in « revert » mode, we repair Windows Sandbox again.

I'm talking about Windows LTSC 2021 and on clean installations of Windows.

I hope this helps.

from privacy.sexy.

Hi @Snowball-V,

Thank you so much. It helps a lot. This was the information missing to take action on three issues and I'm sure your findings will be valuable for so many.

In new patch I will add:

• Explicit documentation in script title that these break Windows Sandbox, Docker and WSL.
• Documentation in caution section with reference to this issue explaining the breaking behavior further.
• Suggest system reboot after running the script (in script docs and terminal output)

Removing these FW scripts would make my life as maintainer easier as they break a lot of stuff. But I think privacy.sexy should consider its public as "consenting adults" (as Python folks would say) and give them a choice with documented implications of their actions. We cannot document this without community report as you did, community testing is only way to create a collective documentation. However, it's too easy to break things now. There will be features such as adding colors for breaking stuff #342, showing warnings for double checking #330 etc. to make it harder to break stuff.

Thank you again and have a nice summer, reading books have become a legacy thing of past but Röda rummet is worth it 🙂.

from privacy.sexy.

0.13.4 is just released 🎉. It improves the documentation:

• Expand the caution notes to explicitly mention the impact on virtualization and isolation features like Windows Sandbox, Docker and WSL.
• Expand script titles to briefly mention affects on these features.
• Expand documentation to suggest system restart.
• Add an informative message to restart the computer in terminal outputs after service changes to ensure the settings are applied.

Thank you @Snowball-V.

Please create new issues for further ideas/problems.

from privacy.sexy.