Windows 10: Registry PERMISSION changes don't persist across boots. No internet.

I reset my Windows 10 system using the built-in method. Everything ran fine, the 4GB update went fine, I installed some software... then the next time I went to start it up, I got "no internet connection" over WiFi.

In order to run the netsh commands to get it back, I have to alter the permissions for
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentContsolSet\Control\Nsi\{eb004a00-9b1a-11d4-9123-0050047759bc}\26 setting FullControl for Everybody.

After that, NETSH runs fine: Code: NETSH int ipv4 reset reset.log[/quote] But once I reboot, I still have no internet connection, the permission flag had been toggled off again, and running NETSH results in another access denied message.

Somehow the internet connection did drift back somehow, but then went away again with the same situation I'm at now.

Other stuff: running CMD in admin mode. WiFi works for all other devices. Reboot router and modem.

Thanks for any help!

:)

 

Windows 10 error 10016 from Run-time broker - cannot change permissions

Right, this is why it's vital to have a known good registry backup before you do any of this!

The first time I tried this, I pressed "Remove" on that dialogue box, which then allowed me to change the permissions, but after rebooting I then found that a lot of my apps no longer worked.

I had to restore the registry to fix this, which put me back to square one of course.

Pressing "Cancel" is no use either, because it then opens the permissions dialogue in read-only mode, and you can't change anything!

I was resigned to this and thought I'd just have to put up with the error messages until I came across the PowerShell script. What it does that is different to what I was doing manually with the registry key permissions I don't know, but I tried again after
running the script, and I pressed "Remove" on the dialogue, fully expecting to find that this had screwed things up again, changed the permissions, and was very pleased to find when I rebooted that all was still working fine!

It's early days yet to tell whether it really has fixed all the error messages, but at least I've now been able to do the whole fix without messing up the system!

Give it a try, as long as you can restore a known good version of the registry if things don't go right, you've nothing to lose.

 

Windows 10 Application Log Event ID 1542 No start button/Windows cannot load classes registry file

According to many people in other threads that doesn't fix the issue. It merely gives a temporary change.

I didn't change permission across the entire registry,not sure where you got that. I'm only replying to be sure whatever MS engineer that may read this can be sure I didn't. I used event logs to troubleshoot permissions in the registry like they're designed
to do.

Personally, I think giving repair advice to people who may or may not have the same issue (symptoms can be the same with different issues) is ill advice. Instead, unification of the recent updates and system configurations would be a good start.