Windows Update Not Working - installation-process of IE 9 and 10 fails

MamuS

MamuS

Member
Joined
Mar 6, 2014
Posts
13
Location
Nuremberg
Hey guys,

I deinstalled IE on my Windows Server 2008 R2 (SBS 2011). Now I wanted to reinstall IE 9 or IE 10, even the Fix-it-Tool and I get the messages:

IE 9: Setup exit code 0x800F081E (-2146498530)
IE 10: Setup exit code: 0x00009C59 (40025)
Fix it: [Code 8004FE2C]

I extracted already the files of the installer.exe and copied it with "robocopy"-cmd-command into the winsxs-folder, and still not working. Any idea? :O

Thanks,
Uwe
 
Hello Uwe, and welcome to Sysnative!

MamuS said:
I extracted already the files of the installer.exe and copied it with "robocopy"-cmd-command into the winsxs-folder, and still not working. Any idea? :O
Click to expand...

This has, unfortunately, caused a lot of damage. Each of those winsxs files has an enormous registry backing to go with it, and just a plain extraction does not create those registry keys/values. All of the automated tools rely on the fact that there is at least some self-consistency between the file system and registry. They're designed to cope with various corruptions, including messed up registry/file system, but not that messed up. Please restore the server to a recent image, and I'll work on that.

Richard
 
Hey Richy,

thanks for your reply! Unfortunately the only backup I had has been stolen as somebody just took my USB-disc. I'm thinking about running a registry-cleaner. Recopying the files in the winsxs-folder was recommended as one of several possibilities from an IT-guy in the net. What about reinstalling e.g. Expression Web, won't be the IE installed too? Or a system-repair from the installation-disc? :O

Regards from Germany,
Uwe


PS.: The problem occured already before recopying the files in the winsxs-folder...
 
MamuS said:
Hey Richy,

thanks for your reply! Unfortunately the only backup I had has been stolen as somebody just took my USB-disc. I'm thinking about running a registry-cleaner. Recopying the files in the winsxs-folder was recommended as one of several possibilities from an IT-guy in the net. What about reinstalling e.g. Expression Web, won't be the IE installed too? Or a system-repair from the installation-disc? :O

Regards from Germany,
Uwe


PS.: The problem occured already before recopying the files in the winsxs-folder...
Click to expand...

Please don't run a registry cleaner. That will make things even worse, and will certainly not help (registry cleaners are a bit like snake oil, they can only safely clean a couple of hundred old registry keys, and out of the millions of registry keys the computer normally processes, it makes absolutely no difference - nothing you will ever notice. On top of this, they quite regularly make mistakes (because they all compete to fix the "most" errors). They're a risk with absolutely no benefit, and certainly won't help a Windows Update problem).

As for the it-guy on the net, I'm sorry to break this to you, but he gave you terrible advice. I've been working with Windows Update for very many years, and you've just got to trust me, just copying the winsxs files won't fix the problem.

I know the problem occurred before them, your root cause remains unchanged, it just breaks all the tools so I can't get to the root cause.

How about a Repair Install? https://www.sysnative.com/forums/wi...-install-windows-windows-7-windows-vista.html


Also, please, if I may be so bold, your server needs better backups. If all your recent images lie on a single memory stick, that isn't adequate backup. (I understand that your data files may be very well backed up, and it's only the image that isn't, in which case I take all this back). Fortunately, it doesn't really matter now, but if you don't have adequate backup, start now so that you have it for when you really need it.

Richard
 
Thanks, Richy!

What I want to avoid is a system repair as I would have to deinstall the servicepacks. This would result e.g. in a new installation of Sharepoint Search Server - means, to install the server from scratch would nearly be the same.

I think, while deinstalling IE, the installer left several entires of cause in the registry, and as you know - sometimes it's just one bloody key blocking the installation. I'm trying to find a solution with the "setup exit code" out of the log-file.

Regards,
Uwe
 
Hey guys,

going ahead with the installation I found the following error-codes in the setup-log-file of IE9 e.g.:

Neutral MSU installation failed (exit code = 0x00000490 (1168))
Language package installation failed (exit code = 0x800f081e (2148468766))
Setup exit code 0x800F081E (-2146498530)

Logfiles of IE 10 and 11 are very similar. Any idea?

Regards,
Uwe



PS.: First error in the CBS-log is:

CBS Failed to open package file: \\?\C:\Windows\Servicing\Packages\Microsoft-Windows-InternetExplorer-VistaPlus-Update~31bf3856ad364e35~amd64~~11.2.9600.16428.mum [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
 
Hello again Uwe,

Do you have a SBS 2011 disk with SP1 integrated into it? If you do, you can avoid uninstalling the service pack.


Alternatively, please let me know what version of IE you currently have on this server, and what version you uninstalled. Next, download and install the System Update Readiness Tool: Fix Windows Update corruption errors such as 0x80070002 and 0x80070057. Finally, please upload all of the logfiles including the entire C:\Windows\Logs\CBS folder. I suspect this won't be fixable, but I don't mind taking a look to see how bad things really are. Maybe, just maybe, it still is.

Richard
 
Thanks, Richy!

I had IE 9, 10 and 11 installed. I deinstalled IE 11 because of problems pasting links into Windows Live Mail, after that, everything was working. For another reason I deinstalled the remaining IE 10 and 9 completely for testing - with the result, that a new installation is not possible.

The logs can be downloaded from my server under http://espritandcompany.dynvpn.de/LOGS_Mamus_Server.zip - hopefully my server will be online while you check this thread. Currently I have no version of IE installed, so I can't use windows-programs such as system-administration or Windows Live Mail any longer...

Thanks for your assistance!
Uwe
 
Thank you for the logs. Unfortunately, I don't bring good news.

Code: 
Found 2134 errors
Fixed 1 errors

Too many to fix. If I attempt to remove the winsxs files you added, I won't get it perfect, so we'll still be looking at an order of several hundred errors in the CheckSUR.log, plus initial root cause, and that would all take far too long, especially with no guaranteed fix at the end. Attempting further, manual, uninstalls is exceptionally risky, and leads to fewer, but more complex errors. That will also take a very long time, with an even lower chance of success.

Windows Update will not work until at an absolute minimum those CheckSUR errors are fixed.

I'm sorry, but I cannot fix this, and I know of nobody who would be willing to take this one (and very few who would be able). If a Repair Install is out of the question, a clean install it is.

In future, I would be more than happy for you to to run any suggestions you find on the internet past me, there's a lot of bad info out there :(

Richard
 
Hey Richy,

thanks for checking the logfiles! The proceeding I found on a forum under www.sevenforums.com. I thought to recopy corrupt manifest-files only, might be, that I deleted wrong files too. Would be interesting what you think about the site of this forum.

Best regards,
Uwe
 
MamuS said:
Hey Richy,

thanks for checking the logfiles! The proceeding I found on a forum under www.sevenforums.com. I thought to recopy corrupt manifest-files only, might be, that I deleted wrong files too. Would be interesting what you think about the site of this forum.

Best regards,
Uwe
Click to expand...

All of the CheckSUR.log entries are actually fairly easy to fix, but none are root cause of your original installation issues. I strongly suspect that you won't repair this issue just by repairing all entries in CheckSUR.log. I would therefore advise against the time investment.

However, if you want to try, there are a further two tutorials covering the same material, a very old one by me (currently on really slow, awful hosting as all the information has now been moved and updated to a private training program here at Sysnative, available for historic reference once): SURT Log Introductory Tutorial | niemiro's Website

and one by Microsoft: Advanced guidelines for diagnosing and fixing servicing corruption
(which I would avoid, IMO both mine and Flavius's are better).

Richard
 
Thanks again, Richy!

Checking the CheckSUR.log I saw, that the (2275) errors are always missing files. So it seems, I or the repair-tool from Microsoft copied the wrong version of the files into the folders (I think I took those extracted out of IE 10 setup.exe). Shell I extract it out of IE 9 or 11?

Regards,
Uwe
 
There's a mixture of all three + updates for base image. Look at the version numbers:

x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.22156_tr-tr_140645cf302f10b8
x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.16441_none_cd4d1ac1f12074aa
x86_microsoft-windows-i..ptdebugui.resources_31bf3856ad364e35_10.2.9200.16521_de-de_6ab3e15a637d53ca
x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_11.2.9600.16518_none_88159ad1fe8cd4f0

This issue is far, far more complex than you realise. What you must consider when repairing each file (or rather, not each "individual", but in blocks of files) is whether that file *should* be present. The SURT is not an infallible tool. If the file should be present, make it present, if it shouldn't, remove it's references from the registry (of which there are too many places to list, but bulk lie in HKEY_LOCAL_MACHINE\COMPONENTS), plus all servicing + manifest references. The SURT reports as it sees, but it does not have the intelligence to understand which way each file should go. There's always a choice to repair or remove each component, and the SURT cannot make that decision.

Believe me, I pride myself in this forum being the go-to place for unfixable Windows Update errors, and this is only the second thread I've turned down this year. It's too big, and too complex.

Richard
 
Highly interesting, Richy!

What I do next is, to extract all files out of all three versions of the IE-Setup.exe (IE 9, 10 and 11) and copying it with robocopy booting with F8 until the command-prompt. Hopefully I have all files of all three versions back again then - then perhaps the error-messages of missing files disappear. After that I'll create new CBS-logfiles and we'll see if the errors are less...

Best regards,
Uwe
 
Hey guys,

I installed IE 10 finally with the following steps:

1. Copy the whole winsxs-folder on another drive (e.g. mounted as E:\) with the cmd-command:
xcopy C:\Windows\winsxs\* E:\Windows\winsxs /s /i

2. Create a new folder on the second drive with the commands:
md E:\Packs\Windows\winsxs\Manifests
md E:\Packs\Windows\servicing\Packages

3. Extract all files out of the IE 9, 10 and 11 Setup.exe (possible with 7-zip):
- all extracted folders in E:\Packs\Windows\winsxs
- all manifest-files in E:\Packs\Windows\winsxs\Manifests
- all cat and mum-files in E:\Packs\Windows\servicing\Packages

4. Copy the folder of step 3 in the folder of step 1 with the following command:
robocopy E:\Packs E:\ /E /IS

5. Download the Runtime-Live-CD ISO-Image and burn it on CD, download under:
http://www.datenrettung-etc.de/runtimelivecd.iso

6. Boot from the CD and hit return, when the red start screen appears:
- assign the drives C: and E:
- delete the original winsxs-folder under C:\Windows\winsxs
- mark and copy the winsxs-folder of E:\Windows\winsxs
- paste it in C:\Windows
- copy all files of E:\Packs\Windows\servicing\Packages
- paste it in C:\Windows\servicing\Packages (if the files are already existing, skip all - if the existing files are older, overwrite it)
- unassign the drives, put out the CD and reboot.

7. Download and run the "System Update Readiness Tool":
Download System Update Readiness Tool for Windows 7 (KB947821) [February 2014] from Official Microsoft Download Center

8. Install the IE in the version you need.

Might be, the proceeding may be different from case to case - but in my case it worked.

Best regards,
Uwe
 
Last edited by a moderator:
Hi Uwe,

Any chance we could see a CheckSUR log please?

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom
 
Hey Tom,

of cause the log-file (together with the IE10_main.log) can be downloaded from my server under www.espritandcompany.com/CheckSUR.zip. Interesting, that there have been around 1500 missing folders, which the tool added automatically (after I added additionally to the extracted files of IE 9 and 10 the extracted files of IE 11 in the winsxs-folder). I don't know, if the remaining 2000 errors of missing files in these folders have been fixed by the installation of the IE 10 - but my system is working fine, and without backup I'll start no more installation or update-proceeding...

Best regards,
Uwe
 
Hi Uwe,

That's a lot of errors! While your system might appear to be problem free now, I can guarantee that you'll run into more problems in the future. I've only had a quick flick through the list to see the files, and some were indeed IE files that may well be in place now, but there are some vital system files missing as well:

Code: 
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-rtlsupport-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-delayload-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-processthreads-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-synch-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-errorhandling-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-debug-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-security-base-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-interlocked-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-memory-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-file-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-fibers-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-misc-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-datetime-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-string-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-heap-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-processenvironment-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-profile-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-console-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-xstate-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-threadpool-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-localization-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-localregistry-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-namedpipe-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-sysinfo-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-handle-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-io-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-libraryloader-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_68c05c919281774d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-util-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-rtlsupport-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-delayload-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-processthreads-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-synch-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-errorhandling-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-debug-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-security-base-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-interlocked-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-memory-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-file-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-fibers-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-misc-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-datetime-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-string-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-heap-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-processenvironment-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-profile-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-console-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-xstate-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-threadpool-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-localization-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-localregistry-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-namedpipe-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-sysinfo-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-handle-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-io-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-libraryloader-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17932_none_0ca1c10dda240617	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-util-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-rtlsupport-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-delayload-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-processthreads-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-synch-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-errorhandling-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-debug-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-security-base-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-interlocked-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-memory-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-file-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-fibers-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-misc-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-datetime-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-string-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-heap-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-processenvironment-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-profile-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-console-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-xstate-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-threadpool-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-localization-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-localregistry-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-namedpipe-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-sysinfo-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-handle-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-io-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-libraryloader-l1-1-0.dll	amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_68d20a7192733a4d	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-util-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-rtlsupport-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-delayload-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-processthreads-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-synch-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-errorhandling-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-debug-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-security-base-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-interlocked-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-memory-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-file-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-fibers-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-misc-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-datetime-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-string-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-heap-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-processenvironment-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-profile-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-console-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-xstate-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-threadpool-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-localization-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-localregistry-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-namedpipe-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-sysinfo-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-handle-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-io-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917	
(f)	CSI Payload File Missing	0x00000000	api-ms-win-core-libraryloader-l1-1-0.dll	x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.18229_none_0cb36eedda15c917

As Richard mentioned earlier, I would highly recommend that you reinstall Windows. You're on bought time at the moment and it's a very big risk continuing to use this computer in it's current state.

Tom
 
Dear Tom,

thanks for your feedback! I'll run the "System Update Readiness Tool" again after backuping - then we'll see, if the installation of the IE 10 added the missing files. Anyway - I don't think, that the files are really missing. I think, these are old entries in the registry, which I could delete, if necessary.

A new installation would be hard, because I have installed and configured several databases and programs, such as IIS 7 with PHP, MySQL, MS-SQL, Sharepoint Search Server, Adobe Flash-Media-Streaming, Microsoft-Smooth-Streaming, Adobe-Master-Collection, Microsoft Expression-Studio, Visual-Studio 2008, 2010 and 2012 Ultimate and a hundred of other programs...

Regards,
Uwe
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top