KB2999226x64 fails claiming not applicable

[nethole]

Started out attempting to play iRacing on windows 7 x64 platform that hasn't been updated in a while. Previously everything had been running in Virtualbox (which was using the windows 7 machine has a hypervisor, so no need to patch . . .)

Down the rabbit hole for Iracing, which requires the 2015 VC++ libraries. This results eventually in a failure for KB2999226 which claims 'not applicable'. Yet, the logs for 2015 VC++ most definitely attempt to install it, and there are enough posts of people needing 2999226 to successfully install it.

I've 'windows updated' the windows 7 system up to the point where it cannot install KB2758694. Post online seem to suggest corruption or .net issues. But I didn't find any successful solutions for the failed XML core services SP3.

So, I'm focusing now on the KB2999226, and why that runtime library will not install. I've attached the CBS.zip

 

[wither 2]

Go into the Windows Update settings and set it to "never check for updates" and reboot. Then try the installation of the problem KB.

 

[nethole]

It was already set to 'never update', been that way for years.

I gave up and installed Windows 10 . . .

Now just dealing with poorer performance with virtualbox , trying to turn off onedrive regularly, and the antimalware software sucking up resources

 

[torchwood]

Hi Nethole,

if you decide to revisit,
The reason it failed

Dism syntax is incorrect, thats what the 2 error codes put together mean

DISM /Online /Add-Package /PackagePath:c:XXXXXXXX\976571\Windows6.1-KB976571-v2-x64.cab /Quiet /NoRestart

or try
wusa.exe C:\XXXXXXXX\Windows6.0-KB934307-x64.msu /quiet /norestart

where XXXX = where .cab or .msu is stored, green = relevant kb



Roy

 

[nethole]

the dism error messages are just a red herring, as they were encountered as I was trying to manually resolve the 'not applicable' issues, and fumbling through commandline options for dism and wusa. Find a way to resolve the 'not applicable' issue so the vc libraries install, then we have a solution...

Until then, no such luck

 

[wither 2]

If the Windows Update was set to never check for updates "for years," I wonder what would have happened if you enabled it. Too late for that.