https://bugs.winehq.org/show_bug.cgi?id=47626
Bug ID: 47626 Summary: Visual studio community 2019 installer not opening Product: Wine Version: 4.13 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dark.shadow4@web.de Distribution: ---
Created attachment 65060 --> https://bugs.winehq.org/attachment.cgi?id=65060 Log with dotnet461 installed
The installer opens a small windows with a progress bar, once that is full it closes and nothing happens anymore.
https://bugs.winehq.org/show_bug.cgi?id=47626
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://visualstudio.micros | |oft.com/downloads/
https://bugs.winehq.org/show_bug.cgi?id=47626
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47626
Roman Pišl rpisl@seznam.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rpisl@seznam.cz
--- Comment #1 from Roman Pišl rpisl@seznam.cz --- Clean wine 4.17 prefix and winetricks -q corefonts dotnet462:
The installer downloads 71MB several times and gives up.
I created offline installation by creating vslayout on Windows box. It seems that the file downloaded in the first step of online installer is vs_installer.opc which is a simple archive containing the actual installer (including nodejs, v8 and even sources..).
Unpacking the archive and running
wine Contents/vs_installer.exe --layoutPath C:/vslayout install --channelId VisualStudio.16.Release --productId Microsoft.VisualStudio.Product.BuildTools --channelUri "https://visualstudio.com" --installChannelUri file:///c:/vslayout/ChannelManifest.json
starts interactive installer, everything works and I can even select required components. But after clicking on the install button an error message box appears that call is not implemented. I was unable to determine what is not implemented, basic WINEDEBUG tricks did not give any useful hint.
If anynone has any idea what is missing, please let me know.
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #2 from Roman Pišl rpisl@seznam.cz --- Created attachment 65455 --> https://bugs.winehq.org/attachment.cgi?id=65455 rstrtmgr fix
Fix for rstrtmgr that avoids "call not implemented" during installation.
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #3 from Roman Pišl rpisl@seznam.cz --- Update:
Clean wine-staging 4.17-git prefix and winetricks -q corefonts dotnet462
rstrtmgr fix applied
I was able to successfully finish installation of visual studio build tools!
https://bugs.winehq.org/show_bug.cgi?id=47626
Aaron Simmons paleozogt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |paleozogt@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #4 from Roman Pišl rpisl@seznam.cz --- 0001-crypt32-Add-MS-root-CA-2010-2011.patch from wine-staging is the only patch that is needed to run vs_installer.exe (from vs_installer.opc) in vanilla wine 4.18.
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #5 from Roman Pišl rpisl@seznam.cz --- Created attachment 65513 --> https://bugs.winehq.org/attachment.cgi?id=65513 Error log while verifying downloaded vs_installer.opc
The only problem remains in stage 1 installer that is unable to verify and unpack downloaded vs_installer.opc. Attaching log WINEDEBUG=error+all,warn+all,fixme+all that appears during the operation.
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #6 from Roman Pišl rpisl@seznam.cz --- Created attachment 65524 --> https://bugs.winehq.org/attachment.cgi?id=65524 Script to run the installer
Patches sent to wine-devel: https://source.winehq.org/patches/data/172150 https://source.winehq.org/patches/data/172151 https://source.winehq.org/patches/data/172152 https://source.winehq.org/patches/data/172153
Attached script demonstrates how to run the installer.
https://bugs.winehq.org/show_bug.cgi?id=47626
Vijay Kamuju infyquest@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |infyquest@gmail.com
--- Comment #7 from Vijay Kamuju infyquest@gmail.com --- All the patches are committed in the source.
https://bugs.winehq.org/show_bug.cgi?id=47626
Roman Pišl rpisl@seznam.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #65455|0 |1 is obsolete| | Attachment #65513|0 |1 is obsolete| |
--- Comment #8 from Roman Pišl rpisl@seznam.cz --- Created attachment 65535 --> https://bugs.winehq.org/attachment.cgi?id=65535 crypt trace during verification
Thank you. I also tracked the problem during stage 1 final verification - see attached log. It seems that CNG_RSA_PUBLIC_KEY_BLOB (0x48) is not handled in crypt32. But that is possibly a bigger task..
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #9 from Roman Pišl rpisl@seznam.cz --- Created attachment 65538 --> https://bugs.winehq.org/attachment.cgi?id=65538 Support for CNG_RSA_PUBLIC_KEY_BLOB
Quickly added support for CNG_RSA_PUBLIC_KEY_BLOB, but then it needs ncrypt.dll and when native is taken, then it needs unimplemented BCryptResolveProviders. No way for now.. Fortunately, the workaround - unpacking the opc file manually - is simple.
https://bugs.winehq.org/show_bug.cgi?id=47626
Roberto Viola cagnulein@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cagnulein@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #10 from Roberto Viola cagnulein@gmail.com --- Thanks everybody to give us a way to install VS2019. I've tried with wine-4.21: the installation goes fine, but when i try to run devenv.exe i encounter this error:
Package Management initialization failed You can get more information by examining the file: ...activitylog.xml (attached)
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #11 from Roberto Viola cagnulein@gmail.com --- Created attachment 65935 --> https://bugs.winehq.org/attachment.cgi?id=65935 vs2019 startup
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #12 from Roberto Viola cagnulein@gmail.com --- Created attachment 65936 --> https://bugs.winehq.org/attachment.cgi?id=65936 error starting vs2019
https://bugs.winehq.org/show_bug.cgi?id=47626
--- Comment #13 from Roman Pišl rpisl@seznam.cz --- Hi Roberto, please keep this bug just for the VS installer itself. There is another bug dedicated to devenv.exe: https://bugs.winehq.org/show_bug.cgi?id=48023
There is also a regression already fixed in git related to midl.exe https://bugs.winehq.org/show_bug.cgi?id=48211 and a regression related to cl.exe not fixed yet: https://bugs.winehq.org/show_bug.cgi?id=48160
I am personally skeptical that the devenv would be functional in the near future, it probably depends on components not implemented at all. But perhaps a wine developer would evaluate it more competently.
https://bugs.winehq.org/show_bug.cgi?id=47626
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Visual studio community |Microsoft Visual Studio |2019 installer not opening |2019 web-installer fails | |due to missing MS root CA | |2010 and rstrtmgr stubs Fixed by SHA1| |5b62f89baa82daecd430897de0b | |b5cab32c5fc5e Status|NEW |RESOLVED URL|https://visualstudio.micros |https://web.archive.org/web |oft.com/downloads/ |/20200308114359/https://dow | |nload.visualstudio.microsof | |t.com/download/pr/57c99182- | |2828-4fc1-8b36-271e2472c838 | |/91d7b8d8ba556b1e8723ca67a0 | |f1e2e4a8274f7dfccbeae567e78 | |b22f0db3f6d/vs_Community.ex | |e CC| |focht@gmx.net Resolution|--- |FIXED Component|-unknown |crypt32 Keywords| |Installer
--- Comment #14 from Anastasius Focht focht@gmx.net --- Hello folks,
please don't abuse bugs as meta-bugs a la "make app x work". Don't link multiple patchsets for different issues to the same bug report. Target each patch(set)/component with an own ticket and use linking feature if they depend on each other.
I'm resolving the ticket here since it has been abused multiple times for different issues.
Reminder for long-time triagers/Wine devs who should know the basic process: Please take action if you see something like this before it's going too far.
* https://source.winehq.org/git/wine.git/commitdiff/5b62f89baa82daecd430897de0... ("crypt32: Add MS root CA 2010.")
* https://source.winehq.org/git/wine.git/commitdiff/c18ebdfe724bd1f3a36bb9136d... ("rstrtmgr: Add stubs RmAddFilter and RmRemoveFilter.")
* https://source.winehq.org/git/wine.git/commitdiff/91570a55c016678c41ea0316b5... ("rstrtmgr: Fake API implementation by returning success.")
Part of Wine 4.19 release.
Thanks Michael and Roman
Whatever is remaining as attached/uncommitted patches: Do yourself a favour and split it out in separate bug reports.
$ sha1sum vs_Community.exe a1f62556079a391f84f95b04606e21c8d62a07a9 vs_Community.exe
$ du -sh vs_Community.exe 1.3M vs_Community.exe
$ wine --version wine-5.3
Regards
https://bugs.winehq.org/show_bug.cgi?id=47626
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 5.4.