KB2617858 The file itself is superseded but not the hotfix, because of the servicing stack, that's why it must be installed. repdrvfs.dll file version: 6.1.7601.21824 Installed file version by another update but a different servicing stack:6.2.9200.16398 You will see that if you install all the updates.
Yes, 2617858 needs to be installed. My comment above was referring the link to the "new" 2617858 abbodi1406 provided. The file he linked to appears identical to the one you already have in the repo. I don't see ver 6.2.9200.16398 of repdrvfs.dll on my system though. Isn't that a Win8 version #?
C:\Windows\System32\wbem\repdrvfs.dll 6.2.9200.16398 Microsoft slowly but surely integrates more and more files from Windows 8. You'll have this file version when you install all updates in LDR mode as I do it.
Okay I see it now- the updated version is coming from KB2506143. Since that one's not part of the core updates, I never installed it. I installed it now as a test and do see version 6.2.9200.16398 on repdrvfs.dll.
About IE10 preview for Win7: Is there a .msu package for it somewhere? And does burfadels v27b install it if it's in .exe format?
The version of this file is 6.1.7601.21824 on my windows. 2750841 and KB2617858 are installed. I forgot a hotfix? Thanks
you can extract the .cab file from the .exe itself. using command: Code: IE10-Windows6.1-x86-en-us.exe /x:C:\IE10 where "C:\IE10" is the folder for the extracted files you do not need to create it prior but installing/integrating the CAB package itself will not work if you do not have the Prerequisites packages installed you can check it in the file SETUPDOWNLOADLIST.txt
Already tried the /X switch before posting and that extracted only 2 text files from the exe. One HWID blocklist and another empty one. So it was utterly useless. Thats why i asked here. But the CAB-s worked fine for me.
@McRip: Update changelogs say KB2739286 has been removed on October 12th but .msp file is still in both x86 and x64 repositories
I ran into a strange problem while testing a build last night in VM with the latest batch of updates. For some strange reason, upon first boot the VM suddenly rebooted and Startup Repair started running automatically. I then found an error in the log saying that ntoskrnl.exe appeared to be corrupt. Startup Repair fixed it, and everything was fine then. Since I had never experienced this particular problem before, I thought I would compare ntoskrnl.exe files from an earlier image and compare it with the ntoskrnl.exe from this last image and I noticed the file version numbers were, indeed, not the same: newer ntoskrnl.exe: 6.1.7601.22124 previous ntoskrnl.exe: 6.1.7601.22103 Is there anyone who has encountered this problem with ntoskrnl.exe, or know what could have caused this? Could it be a VM thing (drivers?) or could it be that the ntoskrnl.exe file really got corrupted? The MD5 hash of the new ntoskrnl.exe (in the install.wim) is C63396902DF72331EFBBBA06986E4A12, but so is the 'repaired' one in the VM install now. So I don't see anything wrong there. EDIT: new VM install from the same .iso did not produce the error (everything worked fine). Must have been a fluke... I hate flukes
Burf... is it possible to run your Superseded Updates Uninstall Script silently... are there any switches? I was wondering if I could call the script to uninstall old updates right after I completed an install.
@burfadel Can your "Installer For Windows Updates" integrate all 3 cab files in WindowsUpdateAgent30-x64.exe into an offline Windows 7 SP1 image? Thank you for your clarification.