[BUG]: Search is still broken even after restore

[MikeSesketcharba]

Description

After restoring all scripts, and then selecting the "strict" preset, (after restarting the system) the windows search feature is still not working. I can't search after pressing the windows key, in the search icon in the task bar, or inside the files explorer.

OS

Windows 10 Pro
Version 1909
18363.418

Reproduction steps

1. Go to select > all
2. Go to revert > selected
3. Run
4. After running, go to select > strict
5. Run
6. Reboot the system

Scripts

privacy-script.zip
privacy-script-restore-all.zip

[undergroundwires]

Hi, does it work if you restore Strict preset?

[MikeSesketcharba]

Hi! After restoring the strict preset, and restarting the computer, seach is still broken in taskbar and files.

Sorry for the delay. I don't have access to my computer regularly.

privacy-script-strict-revert.zip

[undergroundwires]

I am unfortunately not be able to run All selection, it breaks too much for my VMs to be functional.

Test 1:

1. Create clean Windows 10 Pro 1909 (19H2)
2. Run Strict preset
3. Restart the computer
4. Cannot verify that search is still broken in taskbar and files.

Test 2:

1. Create clean Windows 10 Pro 1909 (19H2)
2. Revert all as you mentioned
3. Run Strict preset
4. Restart
5. Cannot verify that search is still broken in taskbar and files.

Search in taskbar	Search in file explorer

If this is caused by privacy.sexy then it's caused by something that's not in Standard/Strict pool and that's not reversible. It's not too many options left. Looking at windows.yaml for scripts that do not have recommend property and that are irreversible would be a painful, but still a way to figure this out. Simple googling of the problem and trying out suggest way would be simpler.

I found something interesting though, running "revert all" caused this start search behavior:

This is obviously not the initial/restored OS state.

I know my response is not helpful at all to you, but good to verify that current Strict preset is fine. There is something causing this issue when reverting all scripts though.

[MikeSesketcharba]

Thank you for testing anyways! Maybe it's about time I reinstalled windows, that ought to fix the problem (and many more I have unrelated to privacy.sexy) If you need me to try any scripts again let me know 9 May 2024 02:02:20 undergroundwires ***@***.***>:

…

I am unfortunately not be able to run *All* selection, it breaks too much for my VMs to be functional. Test 1: 1. Create clean Windows 10 Pro 1909 (19H2) 2. Run Strict preset 3. Restart the computer 4. Cannot verify that search is still broken in taskbar and files. Test 2: 1. Create clean Windows 10 Pro 1909 (19H2) 2. Revert all as you mentioned 3. Run Strict preset 4. Restart 5. Cannot verify that search is still broken in taskbar and files. *Search in taskbar*  *Search in file explorer* image.png (view on web)[https://github.com/undergroundwires/privacy.sexy/assets/15555035/710e0d37-5250-4468-9ae4-971ca08f7319]  image.png (view on web)[https://github.com/undergroundwires/privacy.sexy/assets/15555035/b6ecd573-28fc-4995-8e12-4352b891aef8] If this is caused by privacy.sexy then it's caused by something that's not in Standard/Strict pool and that's not reversible. It's not too many options left. Looking at *windows.yaml[https://github.com/undergroundwires/privacy.sexy/0.13.0/master/src/application/collections/windows.yaml]* for scripts that do not have recommend property and that are irreversible would be a painful, but still a way to figure this out. Simple googling of the problem and trying out suggest way would be simpler. I found something interesting though, running "revert all" caused this start search behavior: image.png (view on web)[https://github.com/undergroundwires/privacy.sexy/assets/15555035/3d5cfd3e-0821-4b2a-9b0b-5d6006954bda] This is obviously not the initial/restored OS state. I know my response is not helpful at all to you, but good to verify that current Strict preset is fine. There is something causing this issue when reverting all scripts though. — Reply to this email directly, view it on GitHub[#358 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AOMC3EY6YUDYF5IYMYQQZ6DZBK4IXAVCNFSM6AAAAABHGIDLU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRGY4DMNBTGY]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/AOMC3E3E5UB3I2WADDJLDILZBK4IXA5CNFSM6AAAAABHGIDLU6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT5IUYKI.gif]