Windows 10: Why are system's MSVC runtime DLLs used instead of ours ones sometimes?

In order to decrease our app's installer size and do not force the user to download MSVC runtime redistributable installer, we include all the MSVC runtime DLLs we need and only them into our installer using the following technique. All was working fine during many years until now. Recently we've switched to use MSVC2022 and 14.42.34433.0 version of the runtime pretty new one. Now, we're getting crash dumps from our users. Not too much about 1 per 1000 users with the following stack trace: msvcp140.dll!00007ffa1d488c34 Unknown myapp.exe!std::_Mutex_base::lock Line 52 C++

:)

 

Msvc++ missing

After upgrading to Windows 10 I tried to launch Origin but I keep getting and error message that the msvc100.dll and msvcr100.dll. After looking through folders I can see that they are there but still won't work. I have tired downloading and installing the
files from microsoft and rebooting several times but I still get the same error messages.

Should I delete the files and if yes, should I delete all of the msvc++ files or just the ones I'm missing? I've tried all the solutions I've seen online but have had no success in fixing this problem.

I would like a step by step solution if anyone is willing.

 

api-ms-win-crt-runtime-l1-1-0-dll is missing

Hi, Oscar_available,

1. If having issues running Dism.exe commands using Command Prompt try using PowerShell (Admin) instead.

2. Follow these steps to fix the issue.

[FIXED] api-ms-win-crt-runtime-l1-1-0.dll is missing error

 

Error: ucrtbase.terminate not located in the dynamic link library api-ms-win-crt-runtime-l1-1-0.dll

Open elevated cmd.
Type the following command: regsvr32 /u api-ms-win-crt-runtime-l1-1-0.dll.
Type the following command: regsvr32 /i api-ms-win-crt-runtime-l1-1-0.dll.
Close cmd. Shut down. Restart.
Here's the page that lists the commands: Regsvr32 - Register a DLL - Windows CMD - SS64.com

That being said, I also did a registry cleaning, and it also had a pending update that went through that was apparently awaiting a full shut down. It might very well have just been that.

Microsoft can nudge all they want, I'm keeping this older model laptop on 7, it's not powerful enough for the bloat of 10. I was very near to running a sfc scan (I was going to make that my last thing to set it to do before retiring to bed for the night) and then putting the windows disc in and repairing the install like you suggested tomorrow if the sfc repair didn't work.