Trouble installing Visual C++ Redistributable 2008 in Windows 11 - Error 1935 - visual-c++

So I recently installed MSI Afterburner on my Windows 11 Machine, but after installing it won't open up. The probable issue was that I didn't have Visual C++ 2008 Redistributable installed. I have all other versions from 2010-2022.
But while installing the 2008 and 2005 redistributables I end up getting a 1935 error and the installer just rolls back.
Error 1935 dialog box
I searched it up and tried everything like running an sfc scan, disabling and enabling the .NET frameworks. I also checked my Registry Editor and it was all correct.
I checked the event logs and found this :
Activation context generation failed for "D:\MSI Afterburner\MSIAfterburner.exe". Dependent Assembly Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.
Then I figured out maybe there was problem with the WinSXS folder's permissions.
Turns out only the TrustedInsaller had full access to the folder and the subfolders.
So, I also tried changing the WinSXS folder's permissions manually, but in vain.
How do I fix this error? How do I change the WinSXS folder's permissions successfully?
Or is there any other fix to get MSI Afterburner up and running? Please help.

This is rather peculiar. I know our systems can differ.
I have installed VS 2022 on a pristine Windows 11 system without MSI Afterburner.
Installed VS 2008 redistributable, no problem.
Again: pristine Windows with MSI Afterburner installed.
Installed VS 2008 redistributable, no errors.
Windows 11 Enterprise, Build 22000.co_release.210604-1628
Redistributable 9.0.21022.8 (2016)
MSI Afterburner 4.6.4 Beta, Riva Server 7.3.2 Beta.
After that installed redistributable 2005, no problem.
Did it happen while installing 2005 redistributable? Did you install any other software? It must be something specific to your system.

Related

InstallShield - Error 429 and missing sabuild.dll

We've recently upgraded from InstallShield 2015 to 2016 SP2. I opened my existing Projects in 2016, and InstallShield upgraded them with no errors. But when I try to build in the GUI I get the following:
Error 429: ActiveX component can't create object
When I try to build using the commandline...
IsCmdBld.exe -p "C:\Path to IS Project file\ProjectFile.ism" -v
...I get the following:
InstallShield (R) Release Builder Copyright (c) 2016 Flexera Software
LLC.
All Rights Reserved.
-1131: Failed to load sabuild.dll.
We have several older versions of InstallShield on the particular machine. These Project files were working fine until I tried building them in 2016. I can open copies of the backed up Project files in 2015 and they still build without error. I have searched the entire computer for "sabuild.dll". None found.
This occurs when I try to build MSI or EXE.
We have InstallShield 2016 SP2 Professional and the update manager says we are on the latest. This is installed on Windows 10 Pro 32-bit (don't ask, I'm not operations and I inherited this setup).
Any thoughts?
Thanks in advance!
Install Microsoft Visual C++ 2013 Redistributable Package.
Also Installshield 2016 originally had an issue with detecting vc++ libraries, so you may need to update to SP2.
Refer IOJ-1742525 on http://helpnet.flexerasoftware.com/installshield23helplib/ReleaseNotes.htm

MicrosoftVisual C++ 2015 Redistributable installation failed 0x80240017

When I try to install Microsoft Visual C++ 2015 Redistributable, I get this error
0x80240017, I need it to solve the api-ms-win-crt-runtime-l1-1-0.dll problem
I had the same problem recently, I needed to use XAMPP and when initializing the Apache module I received this error. I tried many things:
Install all windows updates.
Install Visual C ++ 2015 Redistributable that installs this DLL (I get this error 0x80240017 and could not install).
Install the KBKB2999226 and KB2919355 package that contains this DLL.
Clear TEMP folder and rename directories.
I could not by any means. What solved my problem was to install Visual Studio 2015 itself, I had to push the envelope, I had to push it, that solved my problem, and XAMPP becomes to run, unfortunately.

while installing vc_redist.x64.exe, getting error "Failed to configure per-machine MSU package."

While I am trying to install vc_redist.x64.exe on Windows 8.1
getting following error:
Failed to configure per-machine MSU package.
Posting answer to my own question as I found it here and was hidden in bottom somewhere -
https://social.msdn.microsoft.com/Forums/vstudio/en-US/64baed8c-b00c-40d5-b19a-99b26a11516e/visual-c-redistributable-for-visual-studio-2015-rc-fails-on-windows-server-2012?forum=vssetup
This is because the OS failed to install the required update Windows8.1-KB2999226-x64.msu.
However, you can install it by extracting that update to a folder (e.g. XXXX), and execute following cmdlet. You can find the Windows8.1-KB2999226-x64.msu at below.
C:\ProgramData\Package Cache\469A82B09E217DDCF849181A586DF1C97C0C5C85\packages\Patch\amd64\Windows8.1-KB2999226-x64.msu
copy this file to a folder you like, and
Create a folder XXXX in that and execute following commands from Admin command propmt
wusa.exe Windows8.1-KB2999226-x64.msu /extract:XXXX
DISM.exe /Online /Add-Package /PackagePath:XXXX\Windows8.1-KB2999226-x64.cab
vc_redist.x64.exe /repair
(last command need not be run. Just execute vc_redist.x64.exe once again)
this worked for me.
I would like to give you a background on Universal CRT this would help you in understanding as to why the system should be updated before installing vc_redist.x64.exe.
A large portion of the C-runtime moved into the OS in Windows 10 (ucrtbase.dll) and is serviced just like any other OS DLL (e.g. kernel32.dll). It is no longer serviced by Visual Studio directly. MSU packages are the file type for Windows Updates.
In order to get the Windows 10 Universal CRT to earlier OSes, Windows Update packages were created to bring this OS component downlevel. KB2999226 brings the Windows 10 RTM Universal CRT to downlevel platforms (Windows Vista through Windows 8.1). KB3118401 brings Windows 10 November Update to the Universal CRT to downlevel platforms.
Windows XP (latest SP) is an exception here. Windows Servicing does not provide downlevel packages for that OS, so Visual Studio (Visual C++) provides a mechanism to install the UCRT into System32 via the VCRedist and MSMs.
The Windows Universal Runtime is included in the VC Redist exe package as it has dependency on the Windows Universal Runtime (KB2999226).
Windows 10 is the only OS that ships the UCRT in-box. All prior OSes obtain the UCRT via Windows Update only. This applies to all Vista->8.1 and associated Server SKUs.
For Windows 7, 8, and 8.1 the Windows Universal Runtime must be installed via KB2999226. However it has a prerequisite update KB2919355 which contains updates that facilitate installing the KB2999226 package.
Why does KB2999226 not always install when the runtime is installed from the redistributable? What could prevent KB2999226 from installing as part of the runtime?
The UCRT MSU included in the VCRedist is installed by making a call into the Windows Update service and the KB can fail to install based upon Windows Update service activity/state:
If the machine has not updated to the required servicing baseline, the UCRT MSU will be viewed as being “Not Applicable”.
Ensure KB2919355 is installed. Also, there were known issues with KB2919355 so before this the following hotfix should be installed.
KB2939087
KB2975061
If the Windows Update service is installing other updates when the VCRedist installs, you can either see long delays or errors indicating the machine is busy.
This one can be resolved by waiting and trying again later (which may be why installing via Windows Update UI at a later time succeeds).
If the Windows Update service is in a non-ready state, you can see errors reflecting that.
We recently investigated a failure with an error code indicating the WUSA service was shutting down.
To identify if the prerequisite KB2919355 is installed there are 2 options:
Registry key:
64bit hive
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14
CurrentState = 112
32bit hive
HKLM\SOFTWARE\[WOW6432Node\]Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1.14
CurrentState = 112
Or check the file version of:
C:\Windows\SysWOW64\wuaueng.dll
C:\Windows\System32\wuaueng.dll
is 7.9.9600.17031 or later
I faced a similar problem but in my case I was trying to install Visual C++ Redistributable for Visual Studio 2015 Update 1 on Windows Server 2012 R2. However the root cause should be the same.
In short, you need to install the prerequisites of KB2999226.
In more details, the installation log I got stated that the installation for Windows Update KB2999226 failed. According to the Microsoft website here:
Prerequisites To install this update, you must have April 2014 update
rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
(2919355) installed in Windows 8.1 or Windows Server 2012 R2. Or,
install Service Pack 1 for Windows 7 or Windows Server 2008 R2.
Or, install Service Pack 2 for Windows Vista and for Windows Server
2008.
After I have installed April 2014 on my Windows Server 2012 R2, I am able to install the Visual C++ Redistributable correctly.
The OS failed to install the required update Windows8.1-KB2999226-x64.msu.
However I tried to find the particular update from -
C:\ProgramData\Package Cache\469A82B09E217DDCF849181A586DF1C97C0C5C85\packages\Patch\amd64\Windows8.1-KB2999226-x64.msu.
I couldn't find it there so I installed the kb2999226 update from here (Windows 10 Universal C runtime)
Then I installed the update according to my OS and after that It was working fine.
In my case and while installing VS 2015 on Windows7 64x SP1, I experienced the same so tried to cancel and download/install the KBKB2999226 separately and for some reason the standalone update installer also get stuck searching for updates.
Here what I did:
When the VS installer stuck at the KB2999226 update I clicked cancel.
Installer took me back to confirm cancellation, waited for a while then opened the windows task manager and ended the process of wuse.exe (windows standalone update installer)
On the VS installer clicked "No" to return to installation process. The process was completed without errors.
I also got that error when trying to install the Visual C++ 2015 Redistributable on my Windows 7 SP1 machine.
I solved my problem by installing the Visual C++ 2015-2019 Redistributable from here https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0

VS 2012 Update 3 broke my VS

I am using Windows 8 64 bit machine with VS 2012 ultimate. After installing Update 3 and restarting the machine, I get following error whenever I try to open VS.
---------------------------
devenv.exe - System Error
---------------------------
The program can't start because MSVCR110.dll is missing from your computer. Try reinstalling the program to fix this problem.
---------------------------
OK
---------------------------
The said file is already present in C:\Windows\System32 folder. Please let me know what can be done here..don't want to reinstall that monster again.
You need to check where your projects are being loaded. I have VS installs under both x86 and 64. You'll need downloads for both on a 64 bit operating system.
http://www.microsoft.com/en-us/download/details.aspx?id=14632
http://www.microsoft.com/en-us/download/details.aspx?id=30679
Please see:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/d081943f-fbe8-4a28-b8c0-d83ded9b1a67/msvcr100dll-missing
Some basic tips:
Ensure you have run the install with Administrator rights.
VS won't always ask for a computer restart. However, reboot your computer.
A note about this update.
Note Visual Studio and Team Foundation Server (TFS) installation
mechanics are different. The Visual Studio update installs on top of
whatever is already installed on the computer. The TFS update is a
full layout that replaces whatever is installed on the computer.
Before you try to apply the TFS update, make sure that you have a full
backup of your current databases. If the TFS update installation
fails, you will be unable to restart the update or roll back to the
earlier version of TFS without performing a restore procedure.
http://support.microsoft.com/kb/2835600
If you get this error it means you don't have Microsoft Visual C++ Redistributable 2012 Update 3.Try to download it from http://www.microsoft.com/en-us/download/details.aspx?id=30679 .Hope this helps.
Since it is a 64bit system, copying the missing file to the C:\Windows\SysWOW64 folder should solve your problem. If it keeps failing for other dll just keep copying.
With same error (MSVCR110.dll not found) really reinstalled Microsoft Visual C++ Redistributable 2012 not solved all problems. Some VS tools report - not found msvcr110_clr0400.dll. After repair installation of .net 4.0 (or 4.5/4.5.1) all work fine.

missing header file on a new installation of visual studio 2012

I just installed visual studio 2012 and tried running my C++ project on it.
compilation fails due to missing "SDKDDKVer.h", "windows.h", etc.
I installed the windows 8 sdk from Windows Software Development Kit (SDK) for Windows 8, but after successfully running the installer with the default components (including the windows headers), I can't find any include folder under C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0 or C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A.
I ran the SDK installer twice + tried to repair and still I can't find any trace of the windows header files.
Did anyone encounter something similar?
what am I missing? my OS is win7 x64. I uninstalled VS2010 before installing VS2012.
thanks,
It's a bug caused by VS2012 using the configuration of VS2010.
You have to manually fix the include libraries to get around this (through the property manager).
The substantial modifications needed are :
adding $(WindowsSDK_IncludePath) to the include paths
adding $(WindowsSDK_LibraryPath_x86) or $(WindowsSDK_LibraryPath_x64)
to the library path depending if your building for x84 or x64.
The same problem also exists when you upgrade a VS2010 project to VS2012.
To me, manually fixing the include dirs (see step 1 in previous answer) took care of the problem.

Resources