- Home /
- Visual Studio /
Andreas Schubert
reported
Mar 16, 2017 at 03:51 PM
Solution by
Jeremy Kolb
·
May 31, 2017 at 05:14 PM
This does not appear to be fixed in 15.2 (26430.12)
Solution by
Greg Ingram
·
Jun 12, 2017 at 03:10 PM
I"m still getting the Access Denied error when trying to run a WPF app using v15.3 Preview 2. I have not looked into it much, but still get the error.
Solution by
Greg Ingram
·
Jun 21, 2017 at 04:15 PM
Huy Nguyen sorry for delay. I just noticed your comment. I tried deleting both the privateregistry.bin and privateregistry.user.bin files, opened VS 2017 V3 Preview 2.1 and got the same error.
Solution by
Greg Ingram
·
Jun 22, 2017 at 10:23 AM
I got the Access Denied error later when trying to debug WPF app.
Solution by
Greg Ingram
·
Jun 22, 2017 at 05:02 PM
I tried another test and found something odd. I performed the following:
I did the steps above twice, but saved in different locations.
Having the following apps created in both directories above, I followed your steps and attached with file names labeled to show the one with and without errors while using VS2017. I changed the extension from PML to Log in order to attach. Hope this helps.
Solution by
Alex G
·
Jun 23, 2017 at 03:22 AM
If VS ever creates volatile keys (as Mr. Huy Nguyen hinted), then MS programmers need to keep in mind the following pitfalls:
1. You'll gen an error if you try to create a non-volatile key under a volatile key.
2. If you create a key specifying a few levels of subkeys, Windows will create these levels if they don't exist. BUT if you want to create a volatile subkey, and windows creates those non-existing upper level subkeys for you, they all will be created volatile. If you then try to create a non-volatile subkey under one of those newly created keys, this operation will fail.
Thus, to avoid much grief with volatile subkeys, make sure your RegCreateKey call to create a volatile key takes an existing parent key handle and only creates a single level of volatile subkey.
(Thanks Raymond Chen for the recent article on his blog)
Solution by
Mihai Kanyaro
·
Jul 19, 2017 at 02:07 PM
This issue is beyond annoying. I have version 15.2 installed on Windows 7, and it's the 5th time that I have to delete privateregistry.bin
Thank you MS for selling a beta-level product at full price.
Solution by
John Catenzaro - MSFT [MSFT]
·
Aug 14, 2017 at 03:49 PM
This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://www.visualstudio.com/vs/ Thanks to everyone who provided feedback and votes for this problem.
Solution by
Huy Nguyen [MSFT]
·
Apr 03, 2017 at 11:19 PM
Quick update on the status of this problem:
For "Unknown Error" starting VS on Windows 8.1 or Windows 10: This problem is not related to the private registry file. A fix for this problem is available now for the latest version of both Visual Studio 2017 (https://www.visualstudio.com/vs/) or Visual Studio 2017 Preview (https://www.visualstudio.com/vs/pre).
For "Unknown Error" starting VS or Access Denied on Windows 7:
Please try this work-around first, especially if the current user account is a member of the Administrators group on the machine.
If deleting vspdmc.lock does not work, we will need to reset the private registry file
We've identified 2 potential issues with private registry file on Windows 7 and implemented fixes for them. The fix will be available first on Visual Studio 2017 Preview and we will notify the community when it is.
Best regards,
Huy Nguyen, Visual Studio team
Solution by
Alan Bourke
·
Apr 18, 2017 at 04:33 PM
I am also experiencing what @TranstecJason is experiencing - I updated to v15.1 (26403.7 ) this morning and while it was OK initially I eventually started getting 'Unknown Error' when launching the IDE as normal user or 'run as administrator'. I once again had to delete privateregistry.bin and run the IDE as administrator to get it working again.
232 People are following this
Build Failure. Error: 'path' cannot be an empty string ("") or start with the null character.
1
Solution
Sync of open file to the item on Solution Explorer
1
Solution
Repair reset all my settings
1
Solution
Track Active Item in Solution Explorer no longer works
2
Solution
Inconsistent behaviour with Output Directory and Intermediate Directory (change from VS2015)
1
Solution
Installed extensions getting lost when moving to a new build
1
Solution
ADODB 2.7 reference accepted in VS2015, rejected in VS2017
1
Solution
The "report-a-problem" tool fails silently behind HTTP proxy
2
Solution
Some files not tracked by Solution Explorer
1
Solution