It looks like it began after the update to 1511, but I'm not sure about that. Maybe it happened sometime earlier, since I don't use gpedit.msc too often. A computer with clean install of 1511 does not suffer from this problem.
Anyway, trying to run gpedit.msc now results in "Namespace 'Microsoft.Policies.Sensors.WindowsLocationProvider' is already defined as the target namespace for another file in the store"error message (reported twice).
After clicking OK in that message window, Policy Editor continues to work properly. Apparently we are looking at the same issue as the one described by Microsoft here
Indeed, my policy store has both LocationProviderADM.admxand Microsoft-Windows-Geolocation-WLPAdm.admx, referring to the same namespace (no .adml files though).
Files at that location are protected and not immediately deletable and renamable. What would be the proper way of deleting and renaming these files? Restarting into repair console?
I noticed that also. I've been following the method 1 in your link so far (ignoring it)...
Hmmm... I get the same error
I ended up with a slew of bugs applying the Windows Update to 10586 to my existing installation. For those of you who found 10586 installed cleanly with no errors, did you do a clean install as a new installation? It's near impossible to cleanup my upgrade since even the event viewer doesn't work "Event Viewer cannot open the event log or custom view. Verify the event log service is running or query is too long. The request is not supported." I posted my woes found so far in another thread.
At some point after a lot of cursing I will need to do a fresh install rather than an upgrade. With all the problems I have, I don't trust the built-in recovery. All my user files are stored on s server. It's just that it takes me three days to reinstall all of the applications and cycle through all of the updates. I would prefer to wipe my disk and install 10586 from an ISO, but I haven't found such an ISO. I just have the original ISO from the Win 7, 8, 8.1 upgrade. I wouldn't expect taking that route and then running the windows update to 10586 will give me a different result (that is being a clean working fully functional Win 10 Pro).
Can't speak for your other issue but event vieweris working for me after the upgrade. And I did an in-place upgrade, not a clean install.
Tech BenchI would prefer to wipe my disk and install 10586 from an ISO, but I haven't found such an ISO.
You can also create the ISO image from the media creation tool and it will give you the TH ISO as well. It's what I used to upgrade my desktop with and had no with it. Haven't tried a clean install with it though (yet).Tech Bench
Is it time for another Valium? My in-place upgrade went smoothly, but resulted with a slew of woes I've already noted.Can't speak for your other issue but event vieweris working for me after the upgrade. And I did an in-place upgrade, not a clean install.
Should I ask why it didn't work for me, or ask why it worked for you?
I admit I've never used the media creation tool, but I'm boning up on it now. I have a WDS server which lets me do a remote install. This results in a machine which is a member of my domain and with my domain user account.You can also create the ISO image from the media creation tool and it will give you the TH ISO as well. It's what I used to upgrade my desktop with and had no with it. Haven't tried a clean install with it though (yet).
I'm pretty sure most here will tell you event viewer is working for them. As to why yours doesn't work and mine does, perhaps your system has more issues, I don't know. I just know mine works.Is it time for another Valium? My in-place upgrade went smoothly, but resulted with a slew of woes I've already noted.
Should I ask why it didn't work for me, or ask why it worked for you?
BTW, so you don't think I'm being a smart...s, I've not been able to get my laptop updated so there could be a myriad of issues with this new upgrade.
Peace
