Actually, I create a new system image every month after each Patch Tuesday and can restore to one of those. But it's a lot of hassle and if it turns out that it was just an errant registry key which was causing the problem, I'd likely go ballistic.
Anyway, the registry setting for the Software Policy suggested by technoresult was already set to 23c00 unfortunately. But I'll have a look at the other links in a minute.
I've also been playing around with tool called PolicyPlus available on
Github. But an error appears when trying to install ADMX files which is this one:
I tried enabling a setting using that which was to allow access to the Troubleshooting Wizards, but it appears to have been ignored. But maybe one of the others you suggested will do a better job.
A couple of other suggestions I came across was to delete the profiles located at this location:
Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
The author mentioned that he had four and after deleting them, shutting down and the booting up again Windows detected the NIC and reinstalled it after which the problem was solved. Here's the
link to the post.
However, when I went to the same location I discovered close on 1,000 profiles practically all of which belong to Mullvad VPN. I already mailed them about that. I use a separate Wireguard client rather than their own app and maybe it's gone AWOL and creates repetitious profiles every time I log on. Weird.
Here's a handy
link you might not know about. I was getting the problem he described i.e. Access Denied when trying to run netsh-int-ip-reset. It works perfectly.
Anyway, thanks for trying to help me. I appreciate it very much.