VS Community 2017, 2019 Installation Hozed.

Question

The above are installation nasty grams I get when I install 2017/2019 VS Community. It was suggested I disable PC protection but that didn't help. I've attempted just the IDE, IDE+ASP.NET, IDE et-al and NaDa. There's been some strangeness after updating my OS. Help!

Answer 1

Look at the setup logs as linked in the UI error. Within there it should tell you where it is having permissions problems. Sounds like your OS file security is messed up and/or AV is getting in the way but that would depend on the AV. I know McAfee has historically caused problems but I don't know about newer versions. Norton has also caused problems. But the specific error you're getting leads me towards bad security in the file system.

You might also consider running sfc /scannow to run a system scan to see if it fixes things before you reboot and try again.

Answer 2

No Joy.

Before I attempted to install only ASP.NET I ran sfc /scannow. You'll have to forgive me as I was only into the detail of the OS during the DOS days and I have to get reoriented into this alleged modern system. The scan reveled some correction but I'm not to sure about it's detail. When I reinstalled the same errors appeared. I reviewed the logs, I assume UI=User Interface, from the View link and it indicated that the installer had insufficient privilege's to access a drive.

A while back I thought I'd use my A/B drives for developer SW, A= .exe's and B=program data. I checked sharing and security, all seemed normal. I'm also running the installer from the my admin account and I disabled my AV SW.

The A drive is the problem. Could it be there's some ancient holdover privileging from NT et al the installer can't get around?

Answer 3

The Following is my installation process.

107279-vs-commun-dd-setup-20210620092100-errors.log

The .log shows the offending folder. The following shows the Sharing and security tabs.

I'm Assuming the "read only" att is the offending entity at this time which brings me to the ? of the day.

When I set up the A drive I shared it with everyone, Full, it is owned by Admins, and Users were denied full while Admins had full. I assumed subfolders inherited these permissions and it appears that all have except Program Files (x86), users specifically denied write, but admins aren't in Users. I also noticed a member of NT AUTHORITY\Authenticated Users(S-1-5-11) and NT AUTHORITY\INTERACTIVE (S-1-5-4) in Users. ?????

I was going to wait for a response before I specifically add write to allow in security for PF (x86) folder for Users. Like the Man said "Moum-Back" I used to be on CB radios.

Answer 4

You're not trying to use a network drive to install VS are you? That isn't going to work. VS has to be installed on a local drive so network shares wouldn't matter.

As for read only on the folder, this is irrelevant. Starting back in at least Vista days the UI shows it this way. There is no such thing as a read only folder in Windows technically (since at least 2003). While a folder can have a read only attribute it does nothing. To properly determine the "read only" state of a folder it would require enumerating all files on the folder. Windows doesn't do that for perf reasons so it shows it shaded. You can set or remove it and then it'll apply the attribute to all files within the folder. That is the extent of the purpose of that indicator on a folder. For more info on this you can google the articles on it.

The PF folder is special and normal users don't have permissions to it but TrustedInstaller is the owner and should. On my machine it has full control to this and subfolders. This is the default Windows install so I suspect your default OS folder (probably C) is correct but your A and B are not. You should ensure that these folders have the same permissions. I personally have had some issues with MS STore apps if they aren't installed on the OS drive because it has to recreate the PF and/or PD folders and the permissions don't seem correct. But most apps work OK. I would recommend you sync your permissions on A/B to match C.

Answer 5

Hi @DuGo2Guy

Welcome to Microsoft Q&A!

After analyzing the installation log, you can follow these methods to install Visual Studio.
1). Upgrade your OS to the latest version.
2). Disable the security software on your computer.
3). Run Installer as a administrator.

You can also refer to this document to install Visual Studio.

If your issue still persists, feel free to let me know.

Sincerely,
Peng

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread