Open giogio33 opened 2 months ago
There must be a bug. I cannot post: It results blank and I carefully resubmitted all :(
Please let me know what the problem might be and delete this post. Sorry and thank you
There must be a bug. I cannot post: It results blank and I carefully resubmitted all :(
Please let me know what the problem might be and delete this post. Sorry and thank you
write here once again
Hi I understand what's going on, you need the remove comment specifiers such as <!--
, I will improve the issue creation experience so it will be forms instead to simplify this. I edit your post to fix it 🤗.
OMG 😂
@undergroundwires what i think is that more of the people are selecting full category and not checking what that category contains
For eg selecting Disable app access to personal information
without checking inside it and now getting issue that no apps can access notification
Am I right @undergroundwires
@giogio33, sorry for not being really helpful. This is exactly what I do to find side-effects, bisection with a binary search.
I tested these on Windows 10 22H2 Pro VMs 2024-04-20_01-03-10-privacy-script
but failed to reproduce:
I do not have access to physical Windows machine, which may be need to get the local "login" experience.
I'm not sure which script has this side effect that disables the service that you mention which is the root cause. Please report back if you figure out what has caused it so we can take proper action.
Out-of-topic:
Description
Hi, on two computers I had the same problem after running the same scripts. I debugged for a week and this is what I know now that I can finally work. I worked with image restoration to be able to advance in the debugging.
The problem: After typing the password it hangs forever. sometimes I didn't even get the prompt to login after powerup. After experimenting with Safe mode I discovered that unchecking (not running) the service called "Windows Event Log" I can login although not everything works well. How absurd that a windows logger creates such a serious problem. Congratulation Microsoft.
I then ran Windows Sexy and revert everything that was revertible. This get me to resolve the problem. I will now need to activate one by one, maybe with bisection method since I use image restoration, to see the culprit. Do you have any suggestion where to start from? This will be a slow debug that I can do only when I have more time to go through the image restoration process.
In the attached log file I think that what runs on 2024-04-28 is the revert operation and maybe what runs on 2024-04-19 is what may have created the problem. Not sure. Thank you.
OS
Win 10 Pro 22H2 (OS Build 19045.4355)
Reproduction steps
N/A
Scripts
Runs.zip
Additional information
log file: main.log