Windows 7 Hotfix repository

You need to login to view this posts content.

 

all is ok Installer For Windows Updates V19 is very good

i had to run it as administrator i am in an administrator account but you need to click right on run as administrator

and i saw udaptes in installed udaptes

tanks a lot for your help very appreciate tanks at all

 

when running the uninstaller as admin via right click, it cannot find the text files.

via elevated command prompt is fine however.

also, the USB binary hotfix has disappeared from my MU list.

 

I had problems starting now my pc is very fast to start with these updates

 

You need to login to view this posts content.

 

Doing a fresh install, this is what I was referring to:

Code:

2011-05-18 13:02:08, Info                  CSI    00000001 Shim considered [l:268{134}]"\??\C:\mount\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2011-05-18 13:02:08, Info                  CSI    00000002 Shim considered [l:262{131}]"\??\C:\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2011-05-18 13:02:08, Info                  CBS    Failed to find a matching version for servicing stack: C:\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2011-05-18 13:02:08, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2011-05-18 13:02:08, Info                  CBS    Must be doing offline servicing, using stack version from: C:\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cbscore.dll
2011-05-18 13:02:08, Info                  CBS    Loaded Servicing Stack v6.1.7601.17592 with Core: C:\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cbscore.dll

Now if only there were a log to see if the what SYS files are being used for USB, if the winsxs ones were being used instead of the ones in the \driver folder (thus making USB fix unnecessary)

 

The ones in the driver folder are loaded and locked by Windows in any case, so if the ones in the Winsxs folder are also loaded this is yet another bug as its taking up needless memory and system resources

 

The ones in the system32\drivers folder are used as the active ones. But the USB fix is unnecessary anyway because the versions are correct after the 2529073 update and are still fine after the other USB one. You guys are incorrectly identifying proper behavior as bugs.

 

You need to login to view this posts content.

 

SoLoR you know what would be nice, a newsletter or twitter feed so we can get notified when new updates are available

 

good one, i agree

 

Did the Office updates been deleted?

 

I had read that KB2533552 was giving people trouble, and indeed, during integrating updates to the wim that is the one that failed. I even tried putting it to integrate last in the list, but still failed.

I remember reading that SoLoR said that he experienced other updates failing to install when KB2533552 was already integrated (if I understood correctly). So is it best to just install this one update 'live' then, since it won't take nicely to integration and it may cause problems for other updates integrating?

If there is a way to integrate it successfully and other updates not having problems integrating because of it, is it wise to even try, as 2533552 may become obsolete and then we'd have to remake our 'base' iso again anyway? Or am I missing something here? Thanks...

 

Its not an error, Microsoft blocked it because if you do manage to integrate it then it will cause errors like other pkgmgr updates in the past...so to avoid this its been blocked

The best way to integrate it is to do a reverse integration (same way a service pack is integrated)

 

Thanks for the info to both of you. It appears from what you say there is no clean-cut way to integrate this hotfix, without the possibility of messing with something else. I also noticed it's one of those updates that doesn't have the option to uninstall from the "Programs and Features" window.

What I have done for now is I created a silent installer that contains the two (x64 and x86) versions of the hotfix, which will install at first logon stage (just before booting into desktop upon fresh OS install). I already tested it on both x86 and x64 Win7 and it works. At least that way I know it won't mess with anything.

 

I have done two clean installs with this hotfix sysprep'd and have had no issues

 

by curiosity, the two new Updates take over 250MB once installed, why?

thanks

EDIT: it's advisable to first install the new update, and uninstall the superseded after, or do the opposite?