search

ibay770 / vstudio2022installer

0 stars 0 forks source link

running setup.exe on Windows on ARM results in "The application was unable to start correctly (0xc0000135)." #1

Open sanderjo opened 1 month ago

sanderjo commented 1 month ago

running setup.exe on Windows on ARM results in "The application was unable to start correctly (0xc0000135)."

image

I unpacked the *.7z into a separate directory, and run setup.exe

Tips how to proceed?

C:\Users\super\Downloads\VStudio2022Installer>dir
 Volume in drive C is Windows
 Volume Serial Number is 62F7-094F

 Directory of C:\Users\super\Downloads\VStudio2022Installer

05/10/2024  08:49    <DIR>          .
05/10/2024  08:48    <DIR>          ..
18/07/2024  21:05    <DIR>          Assets
18/07/2024  21:05    <DIR>          cs
18/07/2024  21:05    <DIR>          de
18/07/2024  21:05    <DIR>          es
18/07/2024  21:05    <DIR>          Feedback
18/07/2024  21:05           309.288 feedback.exe
18/07/2024  21:05             1.907 feedback.exe.config
18/07/2024  21:05    <DIR>          fr
18/07/2024  21:05            52.272 InstallCleanup.exe
18/07/2024  21:05               553 InstallCleanup.exe.config
18/07/2024  21:05    <DIR>          it
18/07/2024  21:05    <DIR>          ja
18/07/2024  21:05    <DIR>          ko
18/07/2024  21:05            36.933 NOTICE.txt
18/07/2024  21:05    <DIR>          pl
18/07/2024  21:05    <DIR>          pt-BR
18/07/2024  21:05    <DIR>          resources
18/07/2024  21:05             3.560 Resources.pri
18/07/2024  21:05             2.528 Resources.scale-140.pri
18/07/2024  21:05             2.528 Resources.scale-180.pri
18/07/2024  21:05    <DIR>          ru
18/07/2024  21:05         3.082.296 setup.exe
18/07/2024  21:05             6.105 setup.exe.config
18/07/2024  21:05             9.280 setup.imagemanifest
18/07/2024  21:05               318 setup.visualelementsmanifest.xml
18/07/2024  21:05    <DIR>          TestMsi
18/07/2024  21:05    <DIR>          tr
18/07/2024  21:05            42.544 VSInstallerElevationService.exe
18/07/2024  21:05             4.447 VSInstallerElevationService.exe.config
05/10/2024  08:30        16.949.331 VStudio2022Installer.7z
18/07/2024  21:05           469.456 vswhere.exe
18/07/2024  21:05           206.896 vs_installer.exe
18/07/2024  21:05             2.419 vs_installer.exe.config
18/07/2024  21:05               125 vs_installer.version.json
18/07/2024  21:05               318 vs_installer.visualelementsmanifest.xml
18/07/2024  21:05            31.824 vs_installer.windows.exe
18/07/2024  21:05               265 vs_installer.windows.exe.config
18/07/2024  21:05           206.904 vs_installershell.exe
18/07/2024  21:05             2.419 vs_installershell.exe.config
18/07/2024  21:05               318 vs_installershell.visualelementsmanifest.xml
18/07/2024  21:05           260.680 vs_layout.exe
18/07/2024  21:05             2.419 vs_layout.exe.config
18/07/2024  21:05    <DIR>          zh-Hans
18/07/2024  21:05    <DIR>          zh-Hant
              27 File(s)     21.687.933 bytes
              19 Dir(s)   7.069.859.840 bytes free

C:\Users\super\Downloads\VStudio2022Installer>setup
sanderjo commented 1 month ago

Ah: solved by installing .NET tools via "Windows Features".

Request: can setup.exe detect if dotnet.exe is there, and give a nice meaningful warning if not.

Before, this was not working:

C:\Users\super\Downloads\VStudio2022Installer>dotnet

Usage: dotnet [options]
Usage: dotnet [path-to-application]

Options:
  -h|--help         Display help.
  --info            Display .NET information.
  --list-sdks       Display the installed SDKs.
  --list-runtimes   Display the installed runtimes.

path-to-application:
  The path to an application .dll file to execute.
ibay770 commented 1 month ago

Thank you for the solution! I don't have an ARM PC as yet, so I'm unable to test it out.

sanderjo commented 1 month ago

OK, but my point is: can your tool check for the availiblity of .NET / .dotnet ... and give a nice warning if it's not there? That would be better than the ugly "The application was unable to start correctly (0xc0000135)."

ibay770 commented 1 month ago

It would! Maybe if I had a tool that could find which file gave that error, I could change the string. Someday hopefully.