Forum Discussion
14 Replies
Just an update on Sims 4 problem: I've tried installing The Sims 4 but am getting an error VC+ run time redistributable package was not installed ...
No game files to be found in Program Files (x86) or Program Files.
Please help I miss that pretty green plum bob
@kreepsymusic The first screenshot you've posted is for the EA App's program files, which is not where Sims 4 would be installed by default. But the game isn't installed at all, so that's not relevant at the moment.
Instead, you'll need to manually install, or reinstall, the VC++ runtimes that Sims 4 uses. Start with the 2022 runtimes: Hit Windows key-i, select Apps, scroll down to the Microsoft Visual C++ Redistributables, click on any version from 2015 or later, and select Uninstall. Don't touch the older versions. You can download the newest runtimes directly from Microsoft:
https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170
You'll need both the x86 and x64 versions of the 2015-2022 runtimes, but you can skip the ARM version, which is for a different class of device. Restart your computer after installing and before trying to install Sims 4.
It's worth clearing the App's cache too:
https://help.ea.com/en-us/help/faq/clear-cache-to-fix-problems-with-your-games/
If you get the same error, let me know. If you get a different error, please post a screenshot.
@puzzlezaddict Thank you for the help and info. I removed the Microsoft Visual C++ Redistributables the got the new runtimes.
While I was downloading the Sims 4 I could get access to the Program files, deleted old versions of V C++. I thought that would work .
It did not. see att
I have the new versions of Microsoft Visual C++ Redistributables but I'm not sure how to add them.☹️
@kreepsymusic Like I said, you need to manually install the VC++ runtimes from the download link I posted before. Download the installers and run them, then restart your computer. Don't use the ones within the Sims 4's program files: if those were going to work, they probably would have already.
@puzzlezaddict My computer won't let me uninstall VC runtimes 2010, 2013, or 2015-2022 manually.
I've also tried using CCleaner and System Mechanic to remove them.
They will not uninstall. I've rolled back windows updates too-but I'm still unable to install game.
I guess I'll just have to give up as the only answer for this problem it to replace VC runtimes which I cannot do.
So thanks for your time and help.
@kreepsymusic There's no reason to give up: this problem should absolutely be fixable. First of all, are you signed into an admin account? If not, please do so and then try again. And if you have a third-party antivirus running, it could be getting in the way, so disable it while you're trying to uninstall the runtimes.
If neither of these helps, please let me know what happens when you try to uninstall the runtimes, for example if you get an error, post a screenshot.
@puzzlezaddict I've spent the past several days trying to uninstall vc runtimes.
There are no error msg just the window ding sound. I've tried uninstalling with MicrosoftProgram_Install_and_Uninstall.meta tool and thru command prompt. I set up a new admin acct and tried all the same steps.
I was on remote assistance with Windows for 3 hours and all they did were the same things I've already tried--they couldn't figure out any new method.
I still cannot uninstall or repair vc runtimes.
This has gotten very frustrating I see no solution to this problem anywhere.
Thanks for your time and help.
@kreepsymusic I can only imagine how frustrating this is, but it's also probably the root cause of the problem, so if you can get past it, Sims 4 should work again. Please run a couple of basic checks of your Windows system files:
- Hit Windows key-X
- Choose either “PowerShell (Administrator)” or “Windows Terminal (Administrator),” whichever option is offered
- Inside the window that appears, copy and paste “DISM.exe /Online /Cleanup-image /Checkhealth” without quotes, and enter
- If an error is found, stop here and let me know what it says
- Otherwise, hit Windows key-X and choose “PowerShell (Administrator)” or “Windows Terminal (Administrator)”
- Inside the window, copy and paste “DISM.exe /Online /Cleanup-image /Restorehealth” without quotes, and enter
- The system will start validating soon. If it throws an error, please list it here
- After it reaches 100%, hit Windows key-X again and choose “PowerShell (Administrator)” or “Windows Terminal (Administrator)”
- Inside the window, copy and paste “sfc /scannow” without quotes, and enter
- Post the message you receive here
Restart your computer, hit Windows key-i, select Update & Security, and click the box to check for updates. If any install, restart again afterwards.
You didn't mention whether you have a third-party antivirus installed, but if you do, please disable it, temporarily, before trying again to uninstall the runtimes. Make sure nothing else is running on your computer at the same time, not even a browser window.
If that doesn't work, you can try installing the all-in-one runtimes from here:
https://www.sereby.org/site/downloads/All%20in%20One%20Runtimes
(Make sure to click the small Download button at the bottom of the text box, not some larger flashy Download button at the top of the screen. You don't need to donate money.) This is not as reliable as manually uninstalling and reinstalling, but it's easy enough to try.
If this doesn't work either, let me know, and I'll ask someone for a consult.
@puzzlezaddict corrupt files were found but could not be repaired. Here's the info. Thanks for your help and time.
2023-03-24 16:21:37, Info CSI 000001d6 [SR] Verify complete
2023-03-24 16:21:37, Info CSI 000001d7 [SR] Verifying 100 components
2023-03-24 16:21:37, Info CSI 000001d8 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:38, Info CSI 000001d9 CSIPERF - FilePI Queue 103ms
2023-03-24 16:21:38, Info CSI 000001da [SR] Verify complete
2023-03-24 16:21:38, Info CSI 000001db [SR] Verifying 100 components
2023-03-24 16:21:38, Info CSI 000001dc [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:38, Info CSI 000001dd [SR] Verify complete
2023-03-24 16:21:38, Info CSI 000001de [SR] Verifying 100 components
2023-03-24 16:21:38, Info CSI 000001df [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:39, Info CSI 000001e0 Warning: Overlap: Directory \??\C:\Program Files (x86)\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-shell32, version 10.0.19041.2788, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-shell32, version 10.0.19041.2788, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2023-03-24 16:21:39, Info CSI 000001e1 Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-shell32, version 10.0.19041.2788, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-shell32, version 10.0.19041.2788, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2023-03-24 16:21:39, Info CSI 000001e2 Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-shell32, version 10.0.19041.2788, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-shell32, version 10.0.19041.2788, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2023-03-24 16:21:39, Info CSI 000001e3 Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-shell32, version 10.0.19041.2788, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-shell32, version 10.0.19041.2788, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2023-03-24 16:21:39, Info CSI 000001e4 [SR] Verify complete
2023-03-24 16:21:39, Info CSI 000001e5 [SR] Verifying 100 components
2023-03-24 16:21:39, Info CSI 000001e6 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:40, Info CSI 000001e7 [SR] Verify complete
2023-03-24 16:21:40, Info CSI 000001e8 [SR] Verifying 100 components
2023-03-24 16:21:40, Info CSI 000001e9 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:41, Info CSI 000001ea [SR] Verify complete
2023-03-24 16:21:41, Info CSI 000001eb [SR] Verifying 100 components
2023-03-24 16:21:41, Info CSI 000001ec [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:41, Info CSI 000001ed [SR] Verify complete
2023-03-24 16:21:42, Info CSI 000001ee [SR] Verifying 100 components
2023-03-24 16:21:42, Info CSI 000001ef [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:44, Info CSI 000001f0 CSIPERF - FilePI Queue 2102ms
2023-03-24 16:21:44, Info CSI 000001f1 [SR] Verify complete
2023-03-24 16:21:44, Info CSI 000001f2 [SR] Verifying 100 components
2023-03-24 16:21:44, Info CSI 000001f3 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:45, Info CSI 000001f4 [SR] Verify complete
2023-03-24 16:21:45, Info CSI 000001f5 [SR] Verifying 100 components
2023-03-24 16:21:45, Info CSI 000001f6 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:46, Info CSI 000001f7 [SR] Verify complete
2023-03-24 16:21:46, Info CSI 000001f8 [SR] Verifying 100 components
2023-03-24 16:21:46, Info CSI 000001f9 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:47, Info CSI 000001fa [SR] Verify complete
2023-03-24 16:21:47, Info CSI 000001fb [SR] Verifying 100 components
2023-03-24 16:21:47, Info CSI 000001fc [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:49, Info CSI 000001fd [SR] Verify complete
2023-03-24 16:21:49, Info CSI 000001fe [SR] Verifying 100 components
2023-03-24 16:21:49, Info CSI 000001ff [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:51, Info CSI 00000200 [SR] Verify complete
2023-03-24 16:21:51, Info CSI 00000201 [SR] Verifying 100 components
2023-03-24 16:21:51, Info CSI 00000202 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:52, Info CSI 00000203 [SR] Verify complete
2023-03-24 16:21:52, Info CSI 00000204 [SR] Verifying 100 components
2023-03-24 16:21:52, Info CSI 00000205 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:52, Info CSI 00000206 [SR] Verify complete
2023-03-24 16:21:52, Info CSI 00000207 [SR] Verifying 100 components
2023-03-24 16:21:52, Info CSI 00000208 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:54, Info CSI 00000209 [SR] Verify complete
2023-03-24 16:21:54, Info CSI 0000020a [SR] Verifying 100 components
2023-03-24 16:21:54, Info CSI 0000020b [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:55, Info CSI 0000020c [SR] Verify complete
2023-03-24 16:21:56, Info CSI 0000020d [SR] Verifying 100 components
2023-03-24 16:21:56, Info CSI 0000020e [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:57, Info CSI 0000020f [SR] Verify complete
2023-03-24 16:21:57, Info CSI 00000210 [SR] Verifying 100 components
2023-03-24 16:21:57, Info CSI 00000211 [SR] Beginning Verify and Repair transaction
2023-03-24 16:21:59, Info CSI 00000212 [SR] Verify complete
2023-03-24 16:21:59, Info CSI 00000213 [SR] Verifying 100 components
2023-03-24 16:21:59, Info CSI 00000214 [SR] Beginning Verify and Repair transaction
2023-03-24 16:22:01, Info CSI 00000215 [SR] Verify complete
2023-03-24 16:22:01, Info CSI 00000216 [SR] Verifying 100 components
2023-03-24 16:22:01, Info CSI 00000217 [SR] Beginning Verify and Repair transaction
2023-03-24 16:22:03, Info CSI 00000218 [SR] Verify complete
2023-03-24 16:22:03, Info CSI 00000219 [SR] Verifying 100 components
2023-03-24 16:22:03, Info CSI 0000021a [SR] Beginning Verify and Repair transaction
2023-03-24 16:22:04, Info CSI 0000021b [SR] Verify complete
2023-03-24 16:22:04, Info CSI 0000021c [SR] Verifying 96 components
2023-03-24 16:22:04, Info CSI 0000021d [SR] Beginning Verify and Repair transaction
2023-03-24 16:22:06, Info CSI 0000021e [SR] Verify complete
2023-03-24 16:22:06, Info CSI 0000021f [SR] Repairing 2 components
2023-03-24 16:22:06, Info CSI 00000220 [SR] Beginning Verify and Repair transaction
2023-03-24 16:22:06, Info CSI 00000221 [SR] Cannot repair member file [l:12]'riched20.dll' of Microsoft-Windows-RICHED32, version 10.0.19041.1, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2023-03-24 16:22:06, Info CSI 00000222 [SR] Cannot repair member file [l:12]'riched20.dll' of Microsoft-Windows-RICHED32, version 10.0.19041.1, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2023-03-24 16:22:06, Info CSI 00000223 [SR] This component was referenced by [l:132]'Microsoft-Windows-Client-Desktop-Required-WOW64-Package0015~31bf3856ad364e35~amd64~~10.0.19041.2788.20fa7bc42b98da2d6cc4f49e1f942dfb'
2023-03-24 16:22:06, Info CSI 00000224 [SR] Repairing file \??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\\OneDrive.lnk from store
2023-03-24 16:22:06, Info CSI 00000225 [SR] Repair complete
2023-03-24 16:22:06, Info CSI 00000226 [SR] Committing transaction
2023-03-24 16:22:06, Info CSI 00000227 Creating NT transaction (seq 1)
2023-03-24 16:22:06, Info CSI 00000228 Created NT transaction (seq 1) result 0x00000000, handle @0x8a0
2023-03-24 16:22:06, Info CSI 00000229 Transaction UoW: {9ad3ec31-c9f8-11ed-a2f5-089798e067fc} for BeginTransaction
2023-03-24 16:22:06, Info CSI 0000022a@2023/3/24:20:22:06.890 Beginning NT transaction commit...
2023-03-24 16:22:06, Info CSI 0000022b Transaction UoW: {9ad3ec31-c9f8-11ed-a2f5-089798e067fc} for CommitTransaction
2023-03-24 16:22:06, Info CSI 0000022c@2023/3/24:20:22:06.932 CSI perf trace:
CSIPERF:TXCOMMIT;49164
2023-03-24 16:22:06, Info CSI 0000022d [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2023-03-24 16:24:10, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2023-03-24 16:24:10, Info CBS TiWorker signaled for shutdown, going to exit.
2023-03-24 16:24:10, Info CBS Deleting the contents of directory: \\?\C:\Windows\CbsTemp
2023-03-24 16:24:10, Info CBS Deletion of: \\?\C:\Windows\CbsTemp successful
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2023-03-24 16:24:10, Info CBS Execution Engine Finalize
2023-03-24 16:24:10, Info CBS Execution Engine Finalize
2023-03-24 16:24:10, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2023-03-24 16:24:10, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2023-03-24 16:24:10, Info CBS Ending the TiWorker main loop.
2023-03-24 16:24:10, Info CBS Starting TiWorker finalization.
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2023-03-24 16:24:10, Info CBS CBS Engine already deactivated
2023-03-24 16:24:10, Info CBS CBS Engine already deactivated
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: CoreResourcesUnload
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: SessionManagerFinalize
2023-03-24 16:24:10, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2023-03-24 16:24:10, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: WcpUnload
2023-03-24 16:24:10, Info CSI 0000022e Direct SIL provider: Number of files opened: 202907.
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: DrupUnload
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: CfgMgr32Unload
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: DpxUnload
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: SrUnload
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: CbsEsdUnload
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: CbsEventUnregister
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: AppContainerUnload
2023-03-24 16:24:10, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2023-03-24 16:24:10, Info CBS Ending TiWorker finalization.
2023-03-24 16:24:10, Info CBS Ending the TrustedInstaller main loop.
2023-03-24 16:24:10, Info CBS Starting TrustedInstaller finalization.
2023-03-24 16:24:10, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2023-03-24 16:24:10, Info CBS Ending TrustedInstaller finalization.I forgot no 3rd party antivirus is running Thx
@kreepsymusic Since this suggests other system issues, I'd suggest doing a repair install of Windows. Here's how:
https://www.elevenforum.com/t/repair-install-windows-11-with-an-in-place-upgrade.418/
This allows you to keep all your current data, but if you get to step 14 and are NOT asked if you want to keep your personal files, back out and start over.
Once you've done this, try again to uninstall one of the runtimes.
I will try upgrading to Windows 11 thanks
@kreepsymusic You actually don't need to install Windows 11 if you don't want to. A repair install works on 10 as well, and the instructions are basically identical:
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
But it's your choice, that is if your computer supports 11 at all.
You did it!!!❤️
Thank you so much!🙌