Windows 7 Hotfix repository

The superseded uninstaller runs dism from the Windows\System32 folder. On 32-bit systems, this is the 32-bit version, and on x64 systems it is the 64-bit version. On x64 systems, the 32-bit dism is located in the Windows\syswow64 folder. What it sounds like is for some reason your dism in the system32 folder has been overwritten by the 32-bit version which should be in the syswow64 folder, causing that issue to show. This shouldn't have happened normally, most likely it was manually replaced or stuffed up by a third party tool of some kind.

 

@GLYUKOZA

i dont know if i will do it again. x86 i dont use and so i dont collect the kb for this. we will see.

 

@hanschke
Would be very grateful.

 

@burfadel

Thanks for the clarification.

 

You need to login to view this posts content.

 

You are welcome to do so

 

Not on my part, side effect...they cannot be uninstalled so they are useless showing up in the first place

 

so, there are no updates this sunday?

 

Ricktendo, using your slim NET4, I noticed the Windows\Microsoft.NET folder as you included it in the slim archive is around 300mb, whereas if we perform an administrative install of the .msi's (after applying the hotfixes) via UniExtract that folder is around 225mb. This results in the .7z archive of the x64-x86 files being around 47mb when not doing an administrative install, and around 40mb if we use the msi administrative install method.

Which method do you think we should use when making an installer out of it? I tested the installer made out of the non-administative install files and it works just fine, only the installer is around 47mb of course, as compared to the 40mb one we're used to. What do you think is best to use?

 

Original is bigger because it contains both Client and Extended files, (let me guess) you ONLY did a admin of the client...if you dont want extended files do a second admin install to leave the unneeded files behind

BTW I am working on a MST that will satisfy WU when it comes to KB2468871, these are the x86 full registry entries (I dont have the x64 entries because my laptop is dead)

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\5C1093C35543A0E32A41B090A305076A\Patches\4A3FC9E53BDA08038AFB79A682437085]
"State"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\FCDAC0A0AD874C333A05DC1548B97920\Patches\4A3FC9E53BDA08038AFB79A682437085]
"State"=dword:00000001

 

Hey ricktendo64 thanks for pointing me in the right direction here is the location for x64 I just tested it and it works perfect on my end.

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DFC90B5F2B0FFA63D84FD16F6BF37C4B\Patches\79EB7C9295ED2A736A78A2DD351249A8]
"State"=dword:00000001

 

Thats client right, what is the extendeds product number?

 

about updating KB2584577, mfc42.dll and mfc42u.dll files have version 6.6.8064.0
but the files in system32 have the same version (same KB2506212)

why upgarde?

thanks

 

You know I never install the extended I guess I should start I will get those for you later this evening when I make the updated installer after I add the updates to the MSI's then do an administrative install of the 4 MSI which ProgramsFilesFolder & Windows folders do I use before I 7z the files?

Thanks,
dolivas

 

Hi, just a quick question; I used burfadel's install script and selected to process all updates (option 1) for Solor's update pack (Have updated it according to changelog) and I noticed that there are double copies of certain updates e.g. KB982018 and KB982018_BF. This is on a fresh copy of Win7 SP1. Is this normal or have I done something wrong?

Sorry if this has been asked before.. Cheers