Microsoft C++ 2013 Redistributable X86 Windows 7

0 views
Skip to first unread message

Takako Dito

unread,
Aug 3, 2024, 5:24:23 PM8/3/24
to cladquophyress

I have an old dll that uses the Microsoft Visual C++ 2003 (7.1) run time package. Unfortunately I don't have that DLL around anymore. Short of reinstalling VS2003, is there another way to get the run time redistributable dll?

If you are looking for a file that ends with a "P" such as msvcp71.dll, this indicates that your file was compiled against a C++ runtime (as opposed to a C runtime), in some situations I noticed these files were only installed when I installed the full SDK. If you need one of these files, you may need to install the full .NET 1.1 SDK as well, which is available here: ://www.microsoft.com/en-us/download/details.aspx?id=16217 (106.2 MB)

Also on a side note: be VERY aware of the difference between a Hotfix Update and a Regular Update. As noted in the linked KB932298 download (linked below by Storm): "Please be aware this Hotfix has not gone through full Microsoft product regression testing nor has it been tested in combination with other Hotfixes."

Hotfixes are NOT meant for general users, but rather users who are facing a very specific problem. As described in the article only install that Hotfix if you are have having specific daylight savings time issues with the rules that changed in 2007. -- Likely this was a pre-release for customers who "just couldn't wait" for the official update (probably for some business critical application) -- for regular users Windows Update should be all you need.

Two weeks ago I change my SDD to a new one, and reinstall Windows 11 to it. I have been running Windows 11 since it became available, no major issues, a lot of minor issues, event viewer show a lot of kernel even tracing error but more or less it was working ok. Maybe the biggest issue was that the TPM on the Ryzen 5600x was causing a big one second stutter (apparently its a known issue), so I proceed to turn off on Bios the TPM last week. No more big stutters. Yesterday, I installed AMD Ryzen master to use the Auto OC that I have been using under Windows 10 without no problem (under windows 11 the program was carried from windows 10 but doesn't open). Install the program, it requieres to install Microsoft redistributable c++ 2015 (I think so), everything ok. But here start my problems. Tried the OC, no problem, restart. But when I tried to open Autocad, it takes ages to open; something wasn't happening before. Then, Epic Games Launcher can't be open, or take equally lots of time, like 10 minutes (time where the PC doesn't appear to be doing anything). Then I tried to open Event viewer, but it hangs up and crash. Chrome was usable and responsive, Photoshop the same. Then I proceed to restart, same problem. Then I proceed to run SFC scannow on CMD, an it appears to solve the problem with Autocad and Epic Games Launcher (I think that the event viewer problem was exactly the same, no changes), but if I restart it happens again. Checkdisk and repair with CMD, restart, no changes. Same behavior. Then I proceed to repair Windows from the same PC, restart and same behavior, but I can't install Epic Games Launcher, it stuck on verifying install, and do it too slow. Event viewer the same. I tried to install a fresh Windows 11 from a USB pendrive, the same behavior. Everytime I've deleted the preview partition, format and install. Same odd behavior with event viewer and epic games launcher. Finally, I had to download Windows 10 to a usb pen, install fresh and my PC came back to normal. I can install my Epic Games Launcher, my programs (Twinmotion, autocad, etc). Even viewer shows normal.

@MarshallwarnerI have experienced the same problems today in my up to date Ryzen 3500 Windows 11 PC: Event Viewer not loading and Epic Games Launcher opening but staying in background only. Restarted several times and same situation. I thought it was related to a damaged drive.

I just reinstalled Epic Games Launcher. In the first attempt, installation froze at the "Checking update" window. Tried again and it worked. Not sure what happened, as I was using Epic Games Launcher a few hours ago before the problem started.

Now, I'm unable to open Epic Games Launcher. After rebooting, it stays as a background process using only 7,5 MB of RAM. Event viewer and Microsoft Management Console is also freezing and not responding.

@Kuroch87You are describing the exact same problem I had; believe me, formatting windows 11 again doesn't worked. I tried two times, one with the embedder reset windows, and one with a pen drive. The only thing restore my pc to normal state was going back to windows 10. In every new instalation of Windows 11 event viewer crash, and Epic Games launcher doesn't work normally. Maybe it is a recent windows update, but I don't know, but seems to be a big problem if affects a lot of systems.

@EricToh690Yes, today it tooked about 5 minutes to get to the login screen. According to newer reddit comments, the problem is related to Microsoft Defender. The issue has been reported for AMD Ryzen systems only.

Most things will install easily after you change the bootloader settings (forcelegacyplatform is the big one, and "elamdrivers" obviously refers to early launch anti-malware, basically Windows Defender. At this point you can configure the registry keys and disable the service if it's a problem, though that's not entry level.)

NOTE: If this does not work, then you have to go into WinPE and temporarily move these files / folders (this only works in conjunction with disabling early launch anti-malware.) It is safe to say that most people do not use Windows Defender, as the definitions are terrible compared to most AV tools.

@MarshallwarnerAnother one, I had to go into UEFI and disable "above 4G MIMO," due to it being incompatible with Windows 11 based on my firmware revision (which is why I suggested this bootloader setting, it may have changed without you knowing either.) If you reformat and reinstall, you get a new bootloader. There are easier ways to do this though...

"However, Windows automatically enables PAE when the computer is configured for hot-add memory devices in memory ranges beyond the 4 GB region, as defined by the Static Resource Affinity Table (SRAT). Hot-add memory supports memory devices that you can add without rebooting or turning off the computer."

Of course if your bootloader is corrupted, you can refresh it using this command, but there is a warning that comes with this. It automatically deletes any customizations or other entries (you would have to change the volume letter for the 100MB FAT32 partition reserved for EFI to the letter S via diskpart or another MMC Snap-in, "Disk Management" basically.)

Cakewalk relies on a proper installation of various Microsoft runtime libraries for several components (as do many other Windows programs). You can read more about the Microsoft redistributables here.
While the Cakewalk application only uses the latest runtime libraries, there are other components and plugins that may utilize earlier libraries. Hence the Cakewalk installer additionally installs some of the older versions of these libraries that are used by certain known modules and plugins.

Occasionally the Microsoft runtime libraries installation may get damaged by installing other programs (or even Windows update itself!) by installing incompatible components or removing necessary runtime components that are required for proper operation of Cakewalk. If this happens. the typical symptoms are crashes or hangs on starting Cakewalk or opening a project.

A clean install of Cakewalk will always install the necessary components required for proper operation of the program, and typically restore normal operation. However, its not always convenient to reinstall the application, so we've built a new redistributable installer to help repair a system that doesn't contain all the necessary runtime libraries. You may download the new redistributable installer here.

also cant launch either the cakewalk or pro tools icons ...tried fresh clean with both to no avail......it happened right after jan 1st midnight ...my clock was set to 2064 so i reset the clock and i was never able to launch ...very strange ......so im not really wanting to reinstall windows or reformat ....if something simple ...also i downloaded the fix driver for redistributale for cakewalk above this forum ...no good ....i understand lately that ilok cloud has had issues with pro tools so i checked licences ...no problem there ....nothing launches ....also checked my vst and uninstalled any demo plugins like air or other.....what can be effecting only cakewalk and pro tools ....magix demo is still working fine .......help please ok .....thanks

What likely happened is that when you installed the Magix demo, its installer installed their generic ASIO driver, which is known to cause problems with Cakewalk (and from the looks of it, Pro Tools). If you uninstall your Magix demo, my guess is that Cakewalk (and likely, PT) will start working again.

Programs designed with Visual Studio may require a specific version of the Microsoft Visual C++ Redistributable to run. The requirement resulted in the installation of a large number of Visual C++ Redistributable packages on Windows PCs.

It is not uncommon to see multiple Microsoft Visual C++ Redistributables on a system that were installed by software programs, through updates, e.g. security updates, or manually by the system administrator.

Redistributables are stored in a central location so that any program installed on the system may access the files if required. You can check out our detailed guide on Visual C++ Redistributables here for additional details.

Microsoft changed the system significantly with the release of the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019. A baseline image is provided for these redistributable packages so that it is no longer necessary to install different versions separately on target systems.

From Visual Studio .NET through Visual Studio 2013, each major release of the C++ compiler and tools has included a new, standalone version of the Microsoft C Runtime (CRT) library. These standalone versions of the CRT were independent from, and to various degrees, incompatible with each other. For example, the CRT library used by Visual Studio 2012 was version 11, named msvcr110.dll, and the CRT used by Visual Studio 2013 was version 12, named msvcr120.dll. Beginning in Visual Studio 2015, this is no longer the case. Visual Studio 2015 and later versions of Visual Studio all use one Universal CRT.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages