b3270791

x86 -> http://update.microsoft.com/microsoftupdate/v6/V5Controls/en/x86/client/muweb_site.cab x64 -> http://update.microsoft.com/microsoftupdate/v6/V5Controls/en/x64/client/muweb_site.cab

now, the WU service ad registred as new flag {2}, please read your log file "%windir%\WindowsUpdate.log" 2014-11-27 01:51:02:812 2276 a1c COMAPI ----------- COMAPI: IUpdateServiceManager::AddService2 -----------2014-11-27 01:51:02:812 2276 a1c COMAPI - Service ID = {7971f918-a847-4430-9279-4a52d1efe18d}2014-11-27 01:51:02:812 2276 a1c COMAPI - Allow pending registration = Yes; Allow online registration = Yes; Register service with AU = Yes2014-11-27 01:51:02:812 2276 a1c COMAPI - Authorization cab path = <NULL>and read this -> http://msdn.microsoft.com/en-us/library/windows/desktop/bb394829%28v=vs.85%29.aspx <cite> AddService2 Registers a service with WUA without requiring an authorization cabinet file (.cab), and returns a pointer to an IUpdateServiceRegistration interface. ... If you specify asfAllowPendingRegistration and asfAllowOnlineRegistration together, the update agent immediately attempts to go online to register the service. AddService2 returns S_OK if the registration succeeds. AddService2 returns a failure HRESULT value if the registration fails, but the update agent still attempts to register the service at a later time. </cite> and read into log file: WU client internal API CClientCallRecorder::Register succeeds!!1! before, when the service was down, the flag asfAllowPendingRegistration and asfAllowOnlineRegistration is not set <cite> If you specify neither asfAllowPendingRegistration nor asfAllowOnlineRegistration (in other words, if flags is either zero or asfRegisterServiceWithAU), you must specify a non-NULL path in the authorizationCabPath parameter. In this mode, AddService2 processes the cabinet file (.cab) and registers the service in the same way as IUpdateServiceManager::AddService. </cite> I think that: Microsoft update run fine until the COM server side subrutine have this flag value!!1! the problem was solved server side without releasing a new dll, (muweb.dll) which still contains the expired certificate, good rpc method, until the next release of dll!!1! PS... you can delete the file muauth.cab, you do not need, and will not be created bye ^^

Hi^^ Restore the original dll!!1! The problem has been fixed!!1! however, it seems works without a muauth.cab !!1! bye ^^

if you delete the DataStore.edb, the History of updates is compromised :°°°°

hello * downgrade muweb.dll to r256 and WU&&MU work without delete additional file!!1! X86 http://download.windowsupdate.com/v9/1/microsoftupdate/b/selfupdate/WSUS3/x86/Other/muweb.cab X64 http://download.windowsupdate.com/v9/1/microsoftupdate/b/selfupdate/WSUS3/x64/Other/muweb.cab Bye ^^

hello sir, the file C:\WINDOWS\SoftwareDistribution\AuthCabs\muauth.cab->Authorization.xml have been expired!!1! <ExpiryDate>2014-11-17T17:27:43.5251853-08:00</ExpiryDate> to solve the problem temporarily, please downgrade muweb.dll to -> 7.6.7600.256 see -> http://www.msfn.org/board/topic/173049-windowsmicrosoft-update-not-working-on-windows-2000xp2003/#entry1089383 bye^^