cant run any msi or msu file

I have a Windows 7 64 bit ultimate installation that has been running fine for years. It has been kept off-line and by design has not received any Windows updates in a long time. The computer and all installed software runs fine. But I need an updated version of framework to install a newer program and that requires the service pack before it can be run. So today I went to install service pack and realized that Windows update is no longer working at all.

Using the Windows update feature, whenever I click on check for updates nothing happens. There are no error messages.

I normally prefer to use standalone installs anyway so I downloaded the service pack standalone install from Microsoft. After loading the iso the install routine immediately terminates with what it calls a catastrophic error with no other explanation. Manually clicking on any MSI or MSU file produces the error "installer error 0XC8000247". It doesn't matter what MSI or MSU file I try to run.

I double checked that all of the necessary services were running primarily the Windows update service and the background intelligent transfer service.

I ran SFC /scannow which turned up errors that were NOT repaired. I can't make heads or tails of the CBS log file that is generated (attached). I ran SFC three or four times including once or twice in safe mode. I also ran SFCfix which reported NO errors.

I tried to download the Microsoft fix-it tool but it returns the same install error as other MSI or MSU files (8000247). The same for the update readiness tool. The network troubleshooting tool refuses to run although there doesn't seem to be any networking issues as I can lift the firewall and surf the net fine.

I also tried turning off Windows firewall as well as all other traffic control temporarily which also made no difference.

I have not tried the DSIM command as most everything I read on the Microsoft site said to use the Microsoft fix-it tool instead. Is it safe for me to issue these commands in Windows 7? Do I need to be online for that?

I read somewhere that Intel rapid storage drivers can interfere with Windows update installers. But when I go to the Intel site and attempt to scan my computer to determine what drivers are needed the page returns an error saying it is not able to scan. I read through their explanations, checked my firewalls, etc. to no avail. Without being able to determine exactly what Intel drivers I might need I am reluctant to try to download and install anything for fear of rendering the computer unbootable.

There is no antivirus installed on this machine as it is a DAW that is not intended to ever be on the Internet in any case. Antivirus will interfere with proper operation of the DAW.

I thought about attempting a repair using the Windows install disk but the disc I have would not have the service pack included. I thought about downloading the iso from Microsoft but have held off on that radical approach after reading so much about problems with reactivation etc. after usage. The Windows disk repair is intended primarily for non-bootable systems and checks primarily boot files. I'm not having any of those problems as the computer boots fine and all programs function normally.

I also navigated to the software distribution folder and check the download subfolder which was empty. Nevertheless I stopped Windows update service and deleted the folder and then restarted the service. This made no change.

Re-Installing Windows from scratch on this computer is not possible due to the very large number of programs that would have to be reinstalled from scratch also.

I think the next thing to update is the Intel storage but I'm not sure how to validate exactly which drivers are required for this machine.

Any suggestions on how to proceed are greatly appreciated.

The solution did in fact end up being the Intel rapid storage drivers. This machine was at one point cloned from an older dying one using a universal restore. Apparently the appropriate Intel drivers did not carry over. Installing the latest drivers directly from the motherboard manufacturer did the trick. If someone reads this in the future, avoid downloading more recent drivers directly from Intel and stick with the drivers provided by your motherboard's manufacturer. Worked for me.