Visual Studio Installer Failed (W11 24H2 ARM)

W

WizKid

Member
Messages
38
Reaction score
3
I've kept the "Visual Studio" compatibility option, yet whenever I try to run VS setup, it extracts the files and quits.

I never get the setup wizard.

1742753869100.png

After I click the "Yes" button (and it finishes extracting the files), nothing happens.

Attached is the preset.
 

Attachments

Last edited:
Visual Studio 2022 setup uses:
<c>netframework4wpf 'Windows Presentation Foundation'</c>
Will add it to the Visual Studio compatibility, thank you.
 
nuhi said:
Visual Studio 2022 setup uses:
<c>netframework4wpf 'Windows Presentation Foundation'</c>
Will add it to the Visual Studio compatibility, thank you.
Click to expand...

Now, when trying to install the "Desktop development with C++" workload I get the following error:1742851278824.png
1742851495762.png

Where do I find the installation log?
 
nuhi said:
OK, this one was
<c>powershell32 'PowerShell - 32 bit'</c>
Adding it as well.

Btw if you still would like to remove that component, then install these before Visual Studio:

Seems like they use Powershell to trigger that reboot before continuing installation.

Let me know if that helps.
Click to expand...
Installing the two runtime libraries as listed worked. VS 2022 installed with no errors. :D

I'm guessing the installer uses the 32-bit version of PowerShell to download and install said runtime libraries automatically?

If so, then keeping 'PowerShell (x86)' seems to be superfluous unless one specifically need to.

Maybe you could mention this in the documentation?

One could always extract the MSIs from the installers and put them in the 'post-setup (user)' section.
 
WizKid said:
If so, then keeping 'PowerShell (x86)' seems to be superfluous unless one specifically need to.
Click to expand...
It's not superfluous if you're installing MS products in general.

While there's less of them today, 32-bit versions of MS products continue to exist. Therefore it makes to sense for them to standardize on calling the 32-bit PS for installation reasons. A number of users may never need those products, so they don't notice a problem when removing this component.

You'd probably run into the same problem installing Office add-ons.
 
garlin said:
It's not superfluous if you're installing MS products in general.

While there's less of them today, 32-bit versions of MS products continue to exist. Therefore it makes to sense for them to standardize on calling the 32-bit PS for installation reasons. A number of users may never need those products, so they don't notice a problem when removing this component.

You'd probably run into the same problem installing Office add-ons.
Click to expand...
Very true. Installing those runtimes didn't work:

1743007868696.png

1743008676398.png1743008698806.png
1743008737762.png

So yeah, seems like one does need to keep 'powershell32' after all.
 
Last edited:
You must log in or register to reply here.
Back
Top