Visual Studio 2017 Community Edition - still can't upgrade

Perseverance


Slide Rock State Park, Arizona
(I wanted a picture of something positive
in this blog post!)
Besides my Logitech mouse issue I've also still been working on getting Visual Studio 2017 CE (Community Edition) installed at home but I haven't made any progress.

The MS representative pointed me to a cleanup tool and it's log file, which I've tried many times amongst my other guess work.

In a default installation on a Win7/64 bit OS, the cleanup tool is at:

    C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe

And the log file is at:

    %Temp%\dd_cleanup_YYYYMMDDHHMMSS.log

The log file had a section with a number of lines (actually, about 50 lines) that pointed me in one direction and gave me hope:

Removing File Associations:
Deleting Keys...  
Failed - Requested registry access is not allowed.

When I first installed VS 2017 CE version 15.0, I could not create a solution from a template. The templates were displayed in the "New..." dialog but they didn't do anything. Eventually I found out there was sometimes an issue where the registry settings were configured so that they prevented access and therefore the templates could not be used.

I found a solution on this MSDN web page, specifically the "Hall Crash" user entry using the SubInAcl tool. Once I followed those steps I was able to use the templates. I thought that if I did the same process I might be able to execute the update.

But, of course, I hit another snag. When I'd run the SubInAcl tool using the "/subkeyreg" option, it worked fine by applying the owner and permission updates to all of the subkeys. This time, however, it was not updating the subkeys so I wrote a batch file to output its results and then for the subkeys that I needed to update the owner and permissions, I copied those registry entries and created a separate batch file to run on those keys. Then I'd have to get the list for the next level and repeat the process. It took me a few nights to do that after I got home from my day job.

Today I completed all of that process, ran everything, then crossed my fingers, toes, and eyes and tried to do the upgrade. It ran exactly as urine rich as before.

I've updated my post at the MS Visual Studio web with my new log files. I sure hope those Redmond guys are listening to this poor, helpless dude in Arizona!

Update 5/21/2017


I just noticed that there are 109 other (assumedly) developers following my VS Web post. Apparently I'm not the only one with this issue.

What's up with that picture?

I do photography for a hobby and that's one of my pics. I am very perturbed at this installation issue (especially when combined with my Logitech issue, and an update issue on my Kindle that I'm trying to ignore) and wanted to post something positive. Besides, I don't know what kind of picture to post about this upgrade failure - pictures of fecal matter aren't very pleasant even though it's what kind of bucket filler I've stepped into with this upgrade.

If you're interested, my photography blog (which has been ignored for a while) is at:

https://randymorter.blogspot.com/


Comments

Popular posts from this blog

A better mouse trap - issues with a Logitech Wireless Marathon Mouse M705

Implementing IDisposable Properly

Driver Training - cleaning up unused USB drivers