I'll try to get some professional decision if it's easy enough to repair or not. There's a new section regarding attestation signing, and I'll make an educated guess that this modifies the installer so that it is no longer compatible with Windows 7 hosts. The VirtualBox source code of IsMSCRTInstalled() (in src/VBox/Installer/win/InstallHelper/VBoxInstallHelper.cpp) is unchanged between VirtualBox 7.0.8 and 7.0.10, but not the Makefile.kmk in src/VBox/Installer/win/. The error code 1157 (ERROR_DLL_NOT_FOUND) generally means "One of the library files needed to run this application cannot be found.", but I don't think it's exact enough in this case. The first real difference is indeed the check for the installed runtime. VBoxInstallLog (7.0.10).txt wrote: MSI (c) (A0:44) : Doing action: ca_IsMSCRTInstalledĪction start 15:15:23: ca_IsMSCRTInstalled.ĬustomAction ca_IsMSCRTInstalled returned actual error code 1157 but will be translated to success due to continue markingĪction ended 15:15:25: ca_IsMSCRTInstalled. Consultez également les instructions sur l’installation en mode hors connexion. Pour des instructions sur l’installation et la mise à jour de Visual Studio 2019, consultez Mettre à jour Visual Studio 2019 vers la version la plus récente. If these Windows system libraries aren't enhanced by MS, the Visual C++ stubs don't find the needed entries and that may lead to an application error or crash. Cliquez sur le bouton pour télécharger la dernière version de Visual Studio 2019. So I learned that Visual C++ isn't really a standalone runtime environment but depends on Windows system libraries. But without success, as Visual C++ runtime continued to use the older api-ms-win-downlevel-ole32-l 1-1-0.dll, no matter what I did - some of the Windows internal search paths are hardcoded.Īfter I found these dependencies (many hours with "Dependency Walker"), I had some success by patching the application, but in the end I gave up and migrated to Win 10. I tried many things, including an Win 7 update by KB2952664 ("Telemetry"), it brought a new api-ms-win-downlevel-ole32-l 1-1-1.dll to Win 7 containing this function. In my case, the application called a function "GetErrorInfo" that lead to a lib api-ms-win-downlevel-ole32-l 1-1-1.dll, but in Windows 7 I found api-ms-win-downlevel-ole32-l 1-1-0.dll, that didn't contain this function. fixes - but doesn't port these newer Windows 10 internal library functions backward to Windows 7 - out of service. Now MS develops Visual Studio in a forward direction, so it fits in a serviced Windows 10 library environment that is updated by annual "Feature Updates" and KB. This application was rebuild under a newer Visual Studio in Win 10, after I did an update in my Win 7, the application ended with an error.Īs far as I remember, the Visual Studio (Visual C++ runtime is part of it) relates on Windows delivered libraries, the application is linked against the Visual C++ runtime (or "redistributable package") and Visual C++ runtime lib functions call stub libraries that lead to Windows libraries (or Windows stub libraries that lead to the real Windows libraries, e.g. Don't know if it fits, but I had a similar problem a year ago when I run another application (not related to Virtualbox) in Win 7.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |