The latest bootlog is corrupt. This can happen sometimes.
* * *
Process Monitor
The file 'Bootlog.pml' was not closed cleanly during capture and is corrupt.
OK
* * *
If turning off iCloud doesn't help, a fresh trace is needed.
Proxy Settings Per User - problems
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Can anyone advise me how to stop the 'Proxy settings per user' in the Registry under 'Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings' from returning to Zero everytime I reboot the PC when I want it to stay set at 1. I am not an expert on PC but can sort things out if I'm given clear instructions. I am running the latest up to date version of Windows 10. Many thanks in advance.
Windows for home | Windows 10 | Settings
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
59 answers
Sort by: Oldest
-
Anonymous
2024-10-02T13:55:32+00:00 Hi Ramesh, this is getting stranger and stranger I have run a couple of start ups and each time the system reverted back to 0, I then ran Procman and it all worked fine, it stayed at 0 but I had done nothing else except run the bootlog!
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 71%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Ramesh Srinivasan 87,865 Reputation points Independent Advisor2024-10-02T13:57:22+00:00 Please try another boot trace. The earlier boot log couldn't be opened.
* * *
After enabling the boot trace and rebooting, don't open ProcMon immediately. Instead, wait until ProxySettingPerUser reverts to 0. Then, open ProcMon and save the boot trace.
* * *
-
Anonymous
2024-10-02T13:59:14+00:00 Belay that last one Ramesh it has gone back to 0 I falsely though that the RegEdit ran in real time but it is obviously like a snap shot. Back to square one !!!!
-
Ramesh Srinivasan 87,865 Reputation points Independent Advisor
2024-10-02T14:07:56+00:00 Please see my previous post.