question

DuGo2Guy-5228 avatar image
0 Votes"
DuGo2Guy-5228 asked DuGo2Guy-5228 commented

VS Community 2017, 2019 Installation Hozed.

107020-20171screenshot-2021-06-17-113559.jpg



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!

vs-setup
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

cooldadtx avatar image
0 Votes"
cooldadtx answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DuGo2Guy-5228 avatar image
0 Votes"
DuGo2Guy-5228 answered cooldadtx commented

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?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

You can look at the privileges for the folder that it is having an issue with. There is a feature in the Security tab to view the Effective rights of any user. But installers run in a special TrustedInstaller account so unless you locked down your system then it should have access.

As for privilege holdover, it is possible if you always upgrade your OS in place. But you mentioned NT and AFAIK there has never been an upgrade path from NT to newer OSes so that would be highly unlikely. When you upgrade the OS in place then it won't reset NTFS permissions. But you most likely installed Win10 directly so there shouldn't be any permissions issues.

Can you post the exact error message please? Also post whether TrustedInstaller has full control of the path (using Effective Rights UI) to that path.

0 Votes 0 ·
DuGo2Guy-5228 avatar image
0 Votes"
DuGo2Guy-5228 answered

The Following is my installation process.

107322-workloads.jpg


107277-locations.jpg107278-failed.jpg


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


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

107209-pfx86gentab.jpg107219-pfx86shartab.jpg107323-pfx86sectab.jpg



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.


workloads.jpg (357.2 KiB)
locations.jpg (218.0 KiB)
failed.jpg (110.1 KiB)
pfx86gentab.jpg (49.1 KiB)
pfx86shartab.jpg (53.6 KiB)
pfx86sectab.jpg (57.2 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

cooldadtx avatar image
0 Votes"
cooldadtx answered DuGo2Guy-5228 commented

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.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yippy Skippy!

My VS Community is installing, BUT, B-Advised, it was as a modification of a file subfolder permission and not AV SW or wholesale top level permission modification.

As, in another life, we said; "only the Shadow Know what Lurks in the Heart of Logic Circuits".

I hope this information will help all with future advice.

0 Votes 0 ·

Hi @DuGo2Guy-5228
Do you mean you can successfully install VS Community?
Can you share your experience here? This will help more people to solve their problems.

0 Votes 0 ·

Yes, install successful, save a full C:.

I have other drives that I use for User Apps, but during this process I read a note somewhere that I needed to use C: for SDK installation; tiz a pain in the pa-toot as C filled up quickly.

At any rate, for all those that participated in this exercise I thank you. As an Ooooooold-Timer with little skill with this ?Modern? OS those that pointed out the debugging .log information was the most helpful, the UI logs being the best. From this I was sure I had a Permissions issue. From there I was able to debug the installation Oops to a subdirectory, and this is a guess, that wasn't correctly inheriting permissions. In another life I'd send both HW/SW Engr's as Only the Shadow Know what lurk in the heart of logic circuits to fully asses issues. I digress; after said subfolder ATT/Permissions were adjusted The install completed, regardless of the state of system security SW, AV et al. Now, if I can push the SKD off C: i'd be happy.

0 Votes 0 ·
PengGe-MSFT avatar image
0 Votes"
PengGe-MSFT answered DuGo2Guy-5228 commented

Hi @DuGo2Guy-5228

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


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

My OS is

Edition Windows 10 Pro
Version 21H1
Installed on ‎09-‎Mar-‎21
OS build 19043.1055
Experience Windows Feature Experience Pack 120.2212.2020.0

My HW is:
Processor Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz 3.50 GHz
Installed RAM 32.0 GB
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

I have disabled my AV SW for the installation attempts so bin there, done that.

I have a folder permissions issue, from UI log, that I was waiting on another to confirm as problem as I debug this installation. If you can confirm I'd appreciate.

0 Votes 0 ·