Preventing access to Windows Update website on Windows 7
We run a WSUS server locally and I want to prevent users from accessing the windows update web page via IE or via the "Check online for updates from Windows Update" link on the WU control panel. For our XP systems, there is a group policy setting under "User config/Admin templ/Start Menu/" called "Remove links and access to Windows Update". It worked perfectly on XP but in Vista and Win7, this policy also takes away the "Install Updates" button which prevents them from manually updating via the Windows Update control panel. Only way to install updates is to shutdown, which is somewhat annoying.
Is there any way to get this behavior back so that they can only update from the WSUS and can also install updates on demand instead of just at shutdown? I tried asking this in the Win7 client forum but they couldn't help me.
Thank you.
OK - I can't get Windows 7 x64 RTM or Windows Server 2008 R2 to allow a local domain administrator access to Windows Update. Below are the relevant parts from GPMC's Results modeling for the Windows 7 workstation. I have rebooted the system
to ensure GPUpdate executed.
Computer Configuration
System/Internet Communication Management/Internet Communication settingshide
Policy
Setting
Winning GPO
Turn off access to all Windows Update features
Disabled
WSUS Download and Wait
Turn off Windows Update device driver searching
Disabled
WSUS Download and Wait
Windows Components/Windows Updatehide
Policy
Setting
Winning GPO
Allow Automatic Updates immediate installation
Enabled
WSUS Master
Allow non-administrators to receive update notifications
Enabled
WSUS Master
Allow signed updates from an intranet Microsoft update service location
Enabled
WSUS Master
Configure Automatic Updates
Enabled
WSUS Download and Wait
Configure automatic updating:
5 - Allow local admin to choose setting
The following settings are only required
and applicable if 4 is selected.
Scheduled install day:
0 - Every day
Scheduled install time:
03:00
Policy
Setting
Winning GPO
Delay Restart for scheduled installations
Enabled
WSUS Master
Wait the following period before
proceeding with a scheduled
restart (minutes):
30
Policy
Setting
Winning GPO
Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box
Enabled
WSUS Download and Wait
Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box
Disabled
WSUS Master
Enable client-side targeting
Enabled
WSUS Download and Wait
Target group name for this computer
Wait for Administrator
Policy
Setting
Winning GPO
Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates
Enabled
WSUS Master
No auto-restart with logged on users for scheduled automatic updates installations
Enabled
WSUS Download and Wait
Specify intranet Microsoft update service location
Enabled
WSUS Master
Set the intranet update service for detecting updates:
http://hercules.wakeassoc.com
Set the intranet statistics server:
http://hercules.wakeassoc.com
(example: http://IntranetUpd01)
Policy
Setting
Winning GPO
Turn on recommended updates via Automatic Updates
Enabled
WSUS Master
User Configuration
Windows Components/Windows Updatehide
Policy
Setting
Winning GPO
Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box
Enabled
WSUS Download and Wait
Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box
Disabled
WSUS Download and Wait
Remove access to use all Windows Update features
Disabled
WSUS Download and Wait
Similar Messages
-
Disk Cleanup (Windows Update Cleanup) removes Windows updates
Disk Cleanup (Windows Update Cleanup) removes Windows updates KB3031432,KB3021952, and KB3004375. I have never had this problem before. I use Disk Cleanup after every monthly Microsoft updates. I had to reinstall listed updates on two computers when I checked
for new Windows updates. Why is this? Windows Update Cleanup section of Disk Cleanup should not remove updates. Can not completely cleanup my computers. RodneyCleanup does not removed any updates. Can you check windowsupdate.log file?
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread. -
Where is the forum for Windows Update issues with Windows 10 TP 9926
Trying to find a fix to the Windows Update issue with Windows 10 TP 9926 build and can't find the correct forum to post this question?
This will impact receiving the new build upgrades and will impact test strategy for the new supported OS in our desktop application.Might try them over here.
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update?sort=lastreplydate&dir=desc&tab=Threads&status=&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&tm=1427037339534
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
Where is Support for Windows Update issues for Windows Server?
Where is Support for Windows Update Issues for Windows Server?
Windows Update keeps prompting to install an important update, KB2871690 and continually fails with error code 0x800f922
I ran all the fixes I can find, it still fails.
I also tried the manual install, fails.
Microsoft used to provide no charge support for Windows Update issues. They additionally offer online fixes for other versions of windows, but not server, and I can't find a forum.
I also cannot ignore the update, it continually prompts.
I ran the windowsupdate.diagcab and it continually states it fixes Windows Update error 0x80070057, by resetting windows update data store. It further states it fixes Problems installing recent updates.
But it doesn't. I've run it 50 times, and it says the same thing every time.
So there is no support for windows update, and no support for windowsupdate.diagcab.
What's the deal?I've done the SFC/ SCANNOW and DISM
here is the cbs.log
What are we looking for?
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~BT\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360'. -
CDISMManager::put_ScratchDir
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$Windows.~BT\sources" - CDISMManager::LoadLocalImageSession
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Failed to get and initialize the PE Provider. Continuing by assuming
that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM.EXE:
2013-12-04 19:48:20, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2013-12-04 19:48:20, Info DISM DISM.EXE:
2013-12-04 19:48:20, Info DISM DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
2013-12-04 19:48:20, Info DISM DISM.EXE: Dism.exe version: 6.2.9200.16384
2013-12-04 19:48:20, Info DISM DISM.EXE: Executing command line: X:\$Windows.~BT\sources\dism.exe /logpath:X:\$Windows.~BT\sources\Panther\cbs.log
/scratchdir:X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360 /image:X:\ /is-serviceable
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\FolderProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\FolderProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\WimProvider.dll -
CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\WimProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\VHDProvider.dll -
CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\VHDProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\ImagingProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\ImagingProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\CompatProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\CompatProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2013-12-04 19:48:20, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2013-12-04 19:48:20, Warning DISM DISM.EXE: Failed to load WimManager. Try running from the Deployment Tools Command Prompt. If the issue persists, ensure that wimgapi.dll
and wimserv.exe are up to date.
2013-12-04 19:48:20, Warning DISM DISM.EXE: Failed to add any commands.
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 physical location path: X:\ - CDISMManager::CreateImageSession
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Copying DISM from "X:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD"
- CDISMManager::LoadRemoteImageSession
2013-12-04 19:48:20, Info DISM DISM Image Session: PID=1644 TID=1656 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM OS Provider: PID=1644 TID=1656 Defaulting SystemPath to X:\ - CDISMOSServiceManager::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM OS Provider: PID=1644 TID=1656 Defaulting Windows folder to X:\Windows - CDISMOSServiceManager::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Failed to get and initialize the PE Provider. Continuing by assuming
that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Manager: PID=1612 TID=1616 Image session successfully loaded from the temporary location: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD
- CDISMManager::CreateImageSession
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting Provider OSServices - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM OS Provider: PID=1644 TID=1656 Setting SystemPath to X:\ - CDISMOSServiceManager::SetSystemPath
2013-12-04 19:48:22, Info DISM DISM.EXE: Target image information: OS Version=6.2.9200.16384, Image architecture=amd64
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting the collection of providers from an image provider store type. -
CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM OS Provider: PID=1644 TID=1656 Get the registry path to the SOFTWARE hive located at X:\Windows\system32\config\SOFTWARE
and determine if it is loaded. - CDISMOSServiceManager::DetermineBootDrive
2013-12-04 19:48:22, Info DISM DISM Driver Manager: PID=1644 TID=1656 Further logs for driver related operations can be found in the target operating
system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Current image session is [OFFLINE] - CTransmogManager::GetMode
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Determined WinDir path = [X:\Windows] - CTransmogManager::GetWinDirPath
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Product Type: [ServerNT] - CTransmogManager::Initialize
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
2013-12-04 19:48:22, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1672 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1672 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Processing the top level command token(is-serviceable). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the PE Provider. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Package Manager: PID=1644 TID=1672 Finalizing CBS core. - CDISMPackageManager::Finalize
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM OS Provider: PID=1644 TID=1672 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2013-12-04 19:48:24, Info DISM DISM.EXE:
2013-12-04 19:48:24, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2013-12-04 19:48:24, Info DISM DISM.EXE:
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider -
Windows Update Error 80080005 Windows 7 Client with WSUS 3.0 SP2 server
Hello everyone, I've looked around at other threads related to my issue, and I can't seem to find a correct answer.
I have a computer lab that I've recently installed a Windows 7 Enterprise image onto 35 Dell Optiplex computers (most are 380's, a few older 360's).
I created the image using MDT2010 and used one of the 380's as a reference.
All has been well for about a month or two but recently 6 computers are giving me Windows Update errors with the error code of 80080005.
I have a WSUS 3.0 SP2 server running, and all of my other computers seem to be getting their updates just fine. WSUS has the problematic computers in it's database, but it shows that they haven't checked in for "x" days.
I have Avast 4.8 Professional installed, I have OpenDNS configured to block bad websites, ____, etc. and I also use an Untangle server to prevent access to bad websites. I've ran a Malwarebytes' Anti-Malware scan on the affected computers, as well
as Windows Defender scan, and Windows Live OneCare scans, and all have found no malicious software.
I have also tried resetting the Windows update service as described here: http://support.microsoft.com/kb/971058 as well as a script that supposedly does the same thing, but also resets all previous
update events, but I can't find the script source right now (I had ran it last week, and it didn't work).
I'm currently running a SFC /Scannow on one of the computers, and now it has finished. It gives the error: Windows Resource Protection could not start the repair service. I'll have to google that next.
The last windows update that ran on the computer that I'm working on now was installed on 11-18-2010 and was a Windows Defender Update (KB915597 Def: 1.93.1985.0)
Previous to that was 11/9/2010 2 updates: KB977165 and KB981852.
I guess I'll have to look at all of the other machines to see if they have the same updates installed.
Anyway, has anyone else had this problem? I've seen vista home editions, and RC's but no real Windows 7 Pro+ RTM versions in business environments where updates were controlled by WSUS.
Thanks for any help that you can provide!
By the way, I only work at this location once a week (tuesdays, well thursdays too, but I'm next door to this building, but I have remote access), so bare with me on trying to fix things.Ok, for the sake of completeness, I have completed the instructions given by Miya Yao.
After stopping the Windows Update Service (from an Admin Command prompt window), renaming the SoftwareDistribution folder to SDold, then starting the update service again, I still receive the same error when checking for updates.
The windows update log shows this (starting from about 4am) and I just reset the service at about 9:10, which you can see in the log.
2010-12-21 04:19:02:342 940 f20 Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 04:19:02:342 940 cd4 AU >>## RESUMED ## AU: Search for updates [CallId = {8957B50F-46F1-44C4-A347-20D4C5E91D47}]
2010-12-21 04:19:02:342 940 cd4 AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 04:19:02:342 940 f20 Report CWERReporter finishing event handling. (00000000)
2010-12-21 04:19:02:342 940 cd4 AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 04:19:02:342 940 cd4 AU #########
2010-12-21 04:19:02:342 940 cd4 AU ## END ## AU: Search for updates [CallId = {8957B50F-46F1-44C4-A347-20D4C5E91D47}]
2010-12-21 04:19:02:342 940 cd4 AU #############
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:02:342 940 cd4 AU AU setting next detection timeout to 2010-12-21 14:19:02
2010-12-21 04:19:02:342 940 cd4 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:07:350 940 f20 Report REPORT EVENT: {A472759C-BEE7-4161-84E8-41F1C1D03AB4} 2010-12-21 04:19:02:342-0500 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 80080005 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80080005.
2010-12-21 04:19:07:350 940 f20 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2010-12-21 04:19:07:350 940 f20 Report WER Report sent: 7.4.7600.226 0x80080005 61CA813A-7585-442E-A66B-B0D15CE6BDC0 Scan 101 Managed
2010-12-21 04:19:07:350 940 f20 Report CWERReporter finishing event handling. (00000000)
2010-12-21 04:24:22:767 940 f20 PT WARNING: Cached cookie has expired or new PID is available
2010-12-21 04:24:22:767 940 f20 PT Initializing simple targeting cookie, clientId = a6d6dc1c-d844-451c-8609-3879e6cacb33, target group = , DNS name = lab24.sja.local
2010-12-21 04:24:22:767 940 f20 PT Server URL = http://server2:8530/SimpleAuthWebService/SimpleAuth.asmx
2010-12-21 04:24:22:814 940 f20 Report Uploading 2 events using cached cookie, reporting URL = http://server2:8530/ReportingWebService/ReportingWebService.asmx
2010-12-21 04:24:22:814 940 f20 Report Reporter successfully uploaded 2 events.
2010-12-21 06:59:23:020 940 b4c AU AU was unable to detect updates for more than 48 hours
2010-12-21 06:59:28:027 940 c78 Report REPORT EVENT: {511B1C92-939C-4E97-A51B-50E75FCB7AEF} 2010-12-21 06:59:23:020-0500 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
2010-12-21 06:59:28:027 940 c78 Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:02:03:476 940 2f4 AU Triggering AU detection through DetectNow API
2010-12-21 09:02:03:476 940 2f4 AU Triggering Online detection (interactive)
2010-12-21 09:02:03:476 940 b4c AU #############
2010-12-21 09:02:03:476 940 b4c AU ## START ## AU: Search for updates
2010-12-21 09:02:03:477 940 b4c AU #########
2010-12-21 09:02:03:488 940 b4c AU <<## SUBMITTED ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:03:488 940 e38 Agent *************
2010-12-21 09:02:03:488 940 e38 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:02:03:488 940 e38 Agent *********
2010-12-21 09:02:03:488 940 e38 Agent * Online = Yes; Ignore download priority = No
2010-12-21 09:02:03:488 940 e38 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2010-12-21 09:02:03:488 940 e38 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2010-12-21 09:02:03:488 940 e38 Agent * Search Scope = {Machine}
2010-12-21 09:02:03:488 940 e38 Setup Checking for agent SelfUpdate
2010-12-21 09:02:03:489 940 e38 Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
2010-12-21 09:02:03:489 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:02:03:496 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:071 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:02:06:078 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:080 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:02:06:087 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:100 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:02:06:107 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:123 940 e38 Setup Determining whether a new setup handler needs to be downloaded
2010-12-21 09:02:06:123 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2010-12-21 09:02:06:129 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:129 940 e38 Setup SelfUpdate handler update NOT required: Current version: 7.4.7600.226, required version: 7.4.7600.226
2010-12-21 09:02:06:129 940 e38 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
2010-12-21 09:02:15:386 940 b4c AU AU received policy change subscription event
2010-12-21 09:02:36:165 940 e38 Setup WARNING: Cbs StartSession, error = 0x80080005
2010-12-21 09:02:36:165 940 e38 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" failed, error = 0x80080005
2010-12-21 09:02:36:165 940 e38 Setup FATAL: SelfUpdate check failed, err = 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent * WARNING: Skipping scan, self-update check returned 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent * WARNING: Exit code = 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent *********
2010-12-21 09:02:36:165 940 e38 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:02:36:165 940 e38 Agent *************
2010-12-21 09:02:36:165 940 e38 Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 09:02:36:165 940 e8c AU >>## RESUMED ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:36:165 940 e8c AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 09:02:36:165 940 e8c AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 09:02:36:165 940 e8c AU #########
2010-12-21 09:02:36:165 940 e8c AU ## END ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:36:165 940 e8c AU #############
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:36:165 940 e8c AU AU setting next detection timeout to 2010-12-21 19:02:36
2010-12-21 09:02:36:165 940 e8c AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:41:172 940 e38 Report REPORT EVENT: {678C2913-B3B3-4F14-9310-C2E2B1F3334A} 2010-12-21 09:02:36:165-0500 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 80080005 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80080005.
2010-12-21 09:02:41:172 940 e38 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2010-12-21 09:02:41:172 940 e38 Report WER Report sent: 7.4.7600.226 0x80080005 61CA813A-7585-442E-A66B-B0D15CE6BDC0 Scan 101 Managed
2010-12-21 09:02:41:172 940 e38 Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:06:07:779 940 b4c AU ########### AU: Uninitializing Automatic Updates ###########
2010-12-21 09:06:37:809 940 b4c Handler FATAL: UH: 0x80080005: StartSession failed in CCbs::IsCbsPending
2010-12-21 09:06:37:840 940 b4c Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:06:37:872 940 b4c Service *********
2010-12-21 09:06:37:872 940 b4c Service ** END ** Service: Service exit [Exit code = 0x240001]
2010-12-21 09:06:37:872 940 b4c Service *************
2010-12-21 09:08:37:104 940 e84 Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0500) ===========
2010-12-21 09:08:37:104 940 e84 Misc = Process: C:\Windows\system32\svchost.exe
2010-12-21 09:08:37:104 940 e84 Misc = Module: c:\windows\system32\wuaueng.dll
2010-12-21 09:08:37:104 940 e84 Service *************
2010-12-21 09:08:37:104 940 e84 Service ** START ** Service: Service startup
2010-12-21 09:08:37:104 940 e84 Service *********
2010-12-21 09:08:37:108 940 e84 Agent * WU client version 7.4.7600.226
2010-12-21 09:08:37:108 940 e84 Agent * Base directory: C:\Windows\SoftwareDistribution
2010-12-21 09:08:37:108 940 e84 Agent * Access type: No proxy
2010-12-21 09:08:37:108 940 e84 Agent * Network state: Connected
2010-12-21 09:08:37:453 940 e84 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
2010-12-21 09:08:37:462 940 e84 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2010-12-21 09:08:37:464 940 e84 Agent WARNING: failed to access the auth cab, fatal error 0x80070003
2010-12-21 09:08:37:464 940 e84 Agent WARNING: Invalid service in the backup data store; cleaning up
2010-12-21 09:08:37:465 940 e84 Agent WARNING: Failed to add and register service 7971f918-a847-4430-9279-4a52d1efe18d to the data store 0x80240031
2010-12-21 09:08:37:465 940 e84 Agent WARNING: Default Service Recovery: Attempting to add pending registration for service 7971f918-a847-4430-9279-4a52d1efe18d to the data store
2010-12-21 09:09:22:474 940 e84 Report CWERReporter::Init succeeded
2010-12-21 09:09:22:474 940 e84 Agent *********** Agent: Initializing Windows Update Agent ***********
2010-12-21 09:09:22:475 940 e84 Agent *********** Agent: Initializing global settings cache ***********
2010-12-21 09:09:22:475 940 e84 Agent * WSUS server: http://server2:8530
2010-12-21 09:09:22:475 940 e84 Agent * WSUS status server: http://server2:8530
2010-12-21 09:09:22:475 940 e84 Agent * Target group: (Unassigned Computers)
2010-12-21 09:09:22:475 940 e84 Agent * Windows Update access disabled: No
2010-12-21 09:09:22:475 940 e84 DnldMgr Download manager restoring 0 downloads
2010-12-21 09:09:22:476 940 e84 AU ########### AU: Initializing Automatic Updates ###########
2010-12-21 09:09:22:477 940 e84 AU # WSUS server: http://server2:8530
2010-12-21 09:09:22:477 940 e84 AU # Detection frequency: 22
2010-12-21 09:09:22:477 940 e84 AU # Approval type: Scheduled (Policy)
2010-12-21 09:09:22:477 940 e84 AU # Scheduled install day/time: Every day at 3:00
2010-12-21 09:09:22:477 940 e84 AU # Auto-install minor updates: Yes (Policy)
2010-12-21 09:09:22:478 940 e84 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:09:22:751 940 e84 Report *********** Report: Initializing static reporting data ***********
2010-12-21 09:09:22:751 940 e84 Report * OS Version = 6.1.7600.0.0.65792
2010-12-21 09:09:22:751 940 e84 Report * OS Product Type = 0x00000004
2010-12-21 09:09:22:772 940 e84 Report * Computer Brand = Dell Inc.
2010-12-21 09:09:22:772 940 e84 Report * Computer Model = OptiPlex 380
2010-12-21 09:09:22:775 940 e84 Report * Bios Revision = A01
2010-12-21 09:09:22:775 940 e84 Report * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A01
2010-12-21 09:09:22:775 940 e84 Report * Bios Release Date = 2010-03-11T00:00:00
2010-12-21 09:09:22:775 940 e84 Report * Locale ID = 1033
2010-12-21 09:09:22:777 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:777 940 e84 AU Initializing featured updates
2010-12-21 09:09:22:777 940 e84 AU Found 0 cached featured updates
2010-12-21 09:09:22:777 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:778 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:778 940 e84 AU AU finished delayed initialization
2010-12-21 09:09:27:781 940 36c Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:10:20:421 940 bf0 AU Triggering AU detection through DetectNow API
2010-12-21 09:10:20:422 940 bf0 AU Triggering Online detection (interactive)
2010-12-21 09:10:20:422 940 e84 AU #############
2010-12-21 09:10:20:422 940 e84 AU ## START ## AU: Search for updates
2010-12-21 09:10:20:422 940 e84 AU #########
2010-12-21 09:10:20:425 940 e84 AU <<## SUBMITTED ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:20:425 940 36c Agent *************
2010-12-21 09:10:20:425 940 36c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:10:20:425 940 36c Agent *********
2010-12-21 09:10:20:425 940 36c Agent * Online = Yes; Ignore download priority = No
2010-12-21 09:10:20:425 940 36c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2010-12-21 09:10:20:425 940 36c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2010-12-21 09:10:20:425 940 36c Agent * Search Scope = {Machine}
2010-12-21 09:10:20:425 940 36c Setup Checking for agent SelfUpdate
2010-12-21 09:10:20:426 940 36c Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
2010-12-21 09:10:22:715 940 36c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:10:22:725 940 36c Misc Microsoft signed: Yes
2010-12-21 09:10:22:745 940 36c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:10:22:750 940 36c Misc Microsoft signed: Yes
2010-12-21 09:10:22:765 940 36c Setup Determining whether a new setup handler needs to be downloaded
2010-12-21 09:10:22:765 940 36c Setup SelfUpdate handler is not found. It will be downloaded
2010-12-21 09:10:22:765 940 36c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
2010-12-21 09:10:52:778 940 36c Setup WARNING: Cbs StartSession, error = 0x80080005
2010-12-21 09:10:52:778 940 36c Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" failed, error = 0x80080005
2010-12-21 09:10:52:778 940 36c Setup FATAL: SelfUpdate check failed, err = 0x80080005
2010-12-21 09:10:52:779 940 36c Agent * WARNING: Skipping scan, self-update check returned 0x80080005
2010-12-21 09:10:52:779 940 36c Agent * WARNING: Exit code = 0x80080005
2010-12-21 09:10:52:779 940 36c Agent *********
2010-12-21 09:10:52:779 940 36c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:10:52:779 940 36c Agent *************
2010-12-21 09:10:52:779 940 36c Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 09:10:52:779 940 ba0 AU >>## RESUMED ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:52:780 940 ba0 AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 09:10:52:780 940 ba0 AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 09:10:52:780 940 ba0 AU #########
2010-12-21 09:10:52:780 940 ba0 AU ## END ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:52:780 940 ba0 AU #############
2010-12-21 09:10:52:783 940 ba0 AU Successfully wrote event for AU health state:0
2010-12-21 09:10:52:783 940 ba0 AU AU setting next detection timeout to 2010-12-21 19:10:52
2010-12-21 09:10:52:783 940 ba0 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:10:52:783 940 ba0 AU Successfully wrote event for AU health state:0
2010-12-21 09:10:52:784 940 ba0 AU Successfully wrote event for AU health state:0 -
Unable to Resolve Windows Update Issue in Windows 8.1
Hello,
I recently, as far back as 1 month ago, began experiencing issues with the update service under the Windows 8.1 OS platform.
I found that I was having to repeatedly run the Windows Update Troubleshooting Tool. This appeared to fix the issue with each run of the tool, but eventually I'd have the same problem receiving updates again. My problem is as follows:
1. Windows Update service hangs during register analysis.
2. Unable to reset (stop or restart) wuauserv.
3. Unable to reset (stop or restart) Cryptserv.
4. Unable to reset (stop or restart) BITS.
5. Unit recently, was unable to connect to internet from Desktop GUI, but was able to connect using Metro GUI.
I'm not sure is there was a recent update that caused this issue, but I can no longer download updates for my system, nor can I successfully run the Windows Update Fixit tool.Hi,
Let's confirm these situations:
Now your desktop Internet Explorer can't connect Internet.
You receiving the same updates again and again.
If I am right, please check that update's installation status from update history.
Then refer to this article to troubleshoot:
http://social.technet.microsoft.com/Forums/en-US/c842b997-42a4-41fb-9992-b58d65d068d9/forum-faq-common-steps-to-start-troubleshooting-windows-update-issues?forum=w8itprogeneral
Karen Hu
TechNet Community Support -
Windows Update and the Windows Error reports
31/08/2014 08:41
Windows Error Reporting
Fault bucket 124661653, type 21
Event Name:
WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1:
7.6.7600.320
P2:
80246002
P3: D67661EB-2423-451D-BF5D-13199E37DF28
P4:
Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached
files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.320_888a386ad31bd7d883fbf736bf547a8a1bd5bd9c_150a7995

Analysis
symbol: 
Rechecking for solution: 0
Report Id: 8809d3a9-30ea-11e4-8d08-5442495ff252
Report Status: 0
Does the reference to
D67661EB-2423-451D-BF5D-13199E37DF28
refer to Windows Update Agent and is a scan to find and down the updated version simply failing?
TIA, GerryHi,
This structure is a general Windows Error report structure. There are different meanings for different types.
For the details, you could read this article:
WerReportSetParameter function
http://msdn.microsoft.com/en-us/library/windows/desktop/bb513626(v=vs.85).aspx
For your specific error, we could get these:
P1: 7.6.7600.320 means Windows agent version.
P2: 80246002 means the exact error code
P3: D67661EB-2423-451D-BF5D-13199E37DF28
should be the specific Windows Agent GUID.
Let's verify it:
Look for this GUID in your Windows Update log file located in C:\Windows\WindowsUpdate.log. There you could verify if it's a Windows agent.
Karen Hu
TechNet Community Support -
IT THEN GOES TO THE PAGE
http://go.microsoft.com/fwlink/?LinkID=93504\
I CLOSE THIShello, when this is happening after you've already updated firefox with your admin account, try to delete the ''updates'' folder and ''active-update.xml & updates.xml'' within the %localappdata% folder of your restricted account like it is described in http://kb.mozillazine.org/Software_Update#Software_Update_not_working_properly
-
Windows Update Failed Due To Services Stopped
Generally, the Windows Update issue can be caused by one of the following factors:
I. The Windows Update service has been stopped.
II. Corrupted Windows Update Temporary folder.
In order to narrow down the cause of this issue and resolve it, you can refer to the following steps. After finishing each step, please check the result again on the Windows Update website.
NOTE: Some third party programs can affect the Windows Update service. If you are running any third party applications such as Spyblocker, Internet or web accelerators (programs designed to boost the speed of the Internet connection), security or anti-virus programs (Norton, McAfee, etc.), I recommend we temporarily disable or shut them down and then try accessing Windows Update later. Please understand that you are disabling these programs only for the purpose of troubleshooting and you can re-enable these programs after your finish troubleshooting.
Step 1: Verify the relevant Windows Update services
I. Click the " Start " Button, in “ Search ” bar, type: " services.msc " (without quotes) and press Enter. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
II. Double click the service " Windows Update ".
III. Click on the " General " tab; make sure the " Startup Type " is " Automatic " or " Manual ". Then please click the " Start " button under " Service Status " to start the service.
IV. Please repeat the above steps with the " Background Intelligent Transfer Service " service.
You can also temporarily stop these services, restart the computer, and then start these services again.
Step 2: Rename the Windows Update Softwaredistribution folder
This problem may occur if the Windows Update Software distribution folder has been corrupted. You can refer to the following steps to rename this folder. Please note that the folder will be re-created the next time you visit the Windows Update site.
I. Close all the open windows.
II. Click the " Start " Button, click " All programs ", and click " Accessories ".
III. Right-click " Command Prompt ", and click " Run as administrator ".
IV. In " Administrator: Command Prompt " window, type in " net stop WuAuServ " (without the quotes) and press Enter.
Note : Please look at the cmd window and make sure it says that it was successfully stopped before you try to rename the folder.
V. Click the Start Button, in the " Start Search " box, type in " %windir% " (without the quotes) and press Enter.
VI. In the opened folder, look for the folder named " SoftwareDistribution ".
VII. Right-click on the folder, select Rename and type " SDold " (without the quotes) to rename this folder.
VIII. While still in the " Administrator: Command Prompt " window, type the command " net start WuAuServ " (without the quotes) in the opened window to restart the Windows Updates service.
Note : Please look at the cmd window and make sure it says that it was successfully started .
Clicking Kudos! Is a nice way to say Thank You if this helped you or resolved your problem. Also " Accept It As A Solution" so that others get a benefit from it..
- Aves..thanks phillip, i did that, and i also did it again when the tech who
called me back asked me to do that. it did not work I don't know what
else to do,
i bought adobe package for school which has everything for creative
suite, can i reload disc and only reinstall adobe acrobat and reader?
those are the only two i am having issues with
btw, i scheduled two call back times, and after they called me back
from adobe, i was put on hold for a long time, when the person finally
answered, i was disconnected, tried a second attempt, it happened
again, no return phone call from them, i wasted over 3 hours last
night, with still no solution. -
Windows Update Error Code 8007273D: Cannot Find Solution
When trying to update Windows, I'm running into error code 8007273D. When I click the link "Get help with this error", it takes me to a generic page. After doing a help search for this code, nothing turns up. After surfing the Microsoft website with this code, I just get a bunch of rabbit trails that lead to nothing. It seems that the the person(s) having this problem just kept being sent to different locations for the answer, but never got one. Can anyone help?
Hi,
Generally, the Windows Update issue can be caused by one of the following factors:
1. The Windows Update service has been stopped.
2. Corrupted Windows Update Temporary folder.
In order to narrow down the cause of this issue and resolve it, you can refer to the following steps. After finishing each step, please check the result again on the Windows Update website.
NOTE: Some third party programs can affect the Windows Update service. If you are running any third party applications such as Spyblocker, Internet or web accelerators (programs designed to boost the speed of the Internet connection), security or anti-virus programs (Norton, McAfee, etc.), I recommend we temporarily disable or shut them down and then try accessing Windows Update later. Please understand that we are disabling these programs only for the purpose of troubleshooting and we can re-enable these programs after we finish troubleshooting.
Step 1: Verify the relevant Windows Update services
================================
1. Click the "Start" Button, in “Search” bar, type: "services.msc" (without quotes) and press Enter. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
2. Double click the service "Windows Update".
3. Click on the "General" tab; make sure the "Startup Type" is "Automatic" or "Manual". Then please click the "Start" button under "Service Status" to start the service.
4. Please repeat the above steps with the "Background Intelligent Transfer Service" service.
You can also temporarily stop these services, restart the computer, and then start these services again. If any service is missing or cannot be stopped or restarted, please let me know.
Step 2: Rename the Windows Update Softwaredistribution folder
================================
This problem may occur if the Windows Update Software distribution folder has been corrupted. We can refer to the following steps to rename this folder. Please note that the folder will be re-created the next time we visit the Windows Update site.
1. Close all the open windows.
2. Click the "Start" Button, click "All programs", and click "Accessories".
3. Right-click "Command Prompt", and click "Run as administrator".
4. In "Administrator: Command Prompt" window, type in "net stop WuAuServ" (without the quotes) and press Enter.
Note: Please look at the cmd window and make sure it says that it was successfully stopped before we try to rename the folder. However, if it fails, please let me know before performing any further steps and include any error messages you may have received when it failed.
5. Click the Start Button, in the "Start Search" box, type in "%windir%" (without the quotes) and press Enter.
6. In the opened folder, look for the folder named "SoftwareDistribution".
7. Right-click on the folder, select Rename and type "SDold" (without the quotes) to rename this folder.
8. While still in the "Administrator: Command Prompt" window, type the command "net start WuAuServ" (without the quotes) in the opened window to restart the Windows Updates service.
Note: Please look at the cmd window and make sure it says that it was successfully started. However, if it failed, please let me know before performing any further steps and include any error messages you may have received when it failed.
If the issue persists, to clarify the issue and provide more accurate troubleshooting steps, would you please upload the following information to SkyDrive and provide us the link for analyzing?
How to capture a screenshot
================================
1. Press the Print Screen key (PrtScn) on your keyboard.
2. Click the "Start" Button, type "mspaint" in the Search Bar and Press Enter.
3. In the Paint program, click the "Edit" menu, click "Paste". Then click the "File" menu, and click "Save".
4. The "Save As" dialogue box will appear. Type a file name in the "File name:" box, for example: "screenshot".
5. Make sure "JPEG (*.JPG;*.JPEG;*.JPE;*.JFIF)" is selected in the "Save as type" box, click "Desktop" on the left pane and then click "Save".
How to collect the System Information
================================
1. Click the "Start" Button, type "MSINFO32" in the Search Bar and press Enter to start System Information.
2. On the popup window, on the menu bar, click "File", and click "Save", type a file name and then choose NFO as "Save as type", click "Desktop" on the left pane, and click Save.
How to collect the WindowsUpdate.log file
================================
1. Click the "Start" Button, type "WindowsUpdate.log" (without the quotes) in the Search Bar and Press Enter. We will see a file named "WindowsUpdate.log"
2. Now click on the "File" menu and then click on the "Save As".
3. From the left panel, click "Desktop" and click the Save button.
Arthur Li - MSFT -
Internet Explorer issues after installing Update KB2955163 on Windows 8
Dear,
Since we've installed Windows update KB2955163 on Windows 8, we've been experiencing the following issues:
- After using Internet Explorer for a long while (one hour or longer), some websites won't work properly anymore. For example: list boxes and pop-ups don't appear.
- After using Internet Explorer for a long while (one hour or longer), employees can't access any external webpages. They receive a message saying the webpage isn't available. Reconfiguring the Proxy-settings will temporarily fix this problem.
*The above problems don't appear on all of our computers running Windows 8.
We've found the only fix for these problems, is to uninstall Windows update KB2955163.
All of our affected systems are running Windows 8 Enterprise x64, and come from various manufacturers (Dell / HP etc.).
Is anyone of you guys familiar with these specific issues regarding Windows update KB2955163?
Many thanks in advance,
ThomHi,
Did this issue occur on all computers which installed that update?
In generally, it's not most likely be Windows update cause.
Let's narrow down the issue:
Have you tried to reset the Internet Explorer to check the result:
1.Close all Internet Explorer windows that are currently open.
2.Open the desktop, and then tap or click the Internet Explorer icon on the taskbar. Changing your settings will affect both Internet Explorer and Internet Explorer for the desktop.
3.Tap or click the Tools button, and then tap or click
Internet options.
4.Tap or Click the Advanced tab, and then tap or click
Reset.
5.In the Reset Internet Explorer Settings dialog box, tap or click Reset.
6.When Internet Explorer finishes applying default settings, tap or click
Close, and then tap or click OK. You'll need to restart your PC for these changes to take effect.
If it persists, perform a clean boot to see if it caused by some third-party software:
How to perform a clean boot in Windows
http://support.microsoft.com/kb/929135
Karen Hu
TechNet Community Support -
Windows Update Error (code: 80070490)
Dear Moderator,
I have a problem, i could not use windows update from 3 days ago. I've tried to fix it by system restore, but it didn't work.
I read the information at http://support.microsoft.com/kb/958044, the problem may occur if there is corruption in the Component Based Servicing (CBS) manifest. But the only way to fix it.....I have to repair the instalation of my windows vista by the instalation dvd. Unfortunately, i didn't receive windows vista dvd when i bought my X61 (7676A14).
Dear Moderator, do you have any idea to fix it, please? Coz i already disapointed with this situation.
I hope that Lenovo could consider it and put the instalation file into "Support & Downloads".
Regards,
beJoeI had a similar problem (with a different error code) and below is how I repaired it. In my case, the error turned out to be a mismatch among the windows update files (EXE and DLL) in the c:\windows\system32 folder.
From a Vista computer that WILL do windows updates, copy c:\windows\system32\wu*.* to a flash drive.
Insert the flash drive into the computer with the Windows update problem. On my TP, the flash drive was assigned drive letter F: so I'll use that drive letter in this message. If your system assigns a different drive letter, use that.
At this stage, you won't be able to copy the "good" files to the %windir%\system32 folder and will get "access denied" messages if you try. You probably will, however, see that some of the windows update files in the current %windir%\system32 folder are of different sizes or are older than the "good" files on the flash drive
For security reasons, MS is really serious about stopping anyone at all from writing to the System32 folder. You cannot take ownership of files in the directory through the GUI, but you can do so in a command window. You solve this problem as follows:
Open an elevated command prompt and run the following commands:
FIRST, TAKE OWNERSHIP OF THE WU*.* files in the system 32 directory using this command.
takeown /f c:\windows\system32\wu*.*
NEXT, GIVE OWNERSHIP PRIVILEGES TO ALL MEMBERS OF THE ADMINISTRATOR GROUP using this command:
icacls c:\windows\system32\wu*.* /GRANT ADMINISTRATORS:F
Then, having vanquished the troublesome "access denied" message, run this command:
copy f:\wu*.* c:\windows\system32\*.*
When prompted, allow each current WU*.* file in the system32 to be overwritten.
On my ThinkPad, Windows Update worked after I performed the above steps.
If this makes you nervous, it should as you are messing with (and may mess up) the folder with some of the most important operating system files. If you're not experienced, get someone who is experienced to try this.
Oh, and by the way, run a rescue and recovery or other program to image your disk before you do any of these things.
Good luck. -
Windows Updates Error Codes 80070308 and 80070643
Recently I have a problem with windows updates patches for this month (June 2014). I updated 10 computers (at office), 9 of them have either the error codes 80070308 and/or 80070643. I tried to disable the Symantec Endpoint, used the Microsoft
.NET Framework Repair Tool to fix the .Net Framework related error but still have failure. I can still finish all the failed patches by rescanning the PC than install them; however; I still have 40 PCs need to be patched. How do I prevent
the installation failure, all the PCs have no problem at last month. Any suggestion, many thanks.Hi,
If your computer is having problems finding and installing operating system update, I suggest to
try the windows update troubleshooter.
To run a Windows Update troubleshooter:
http://windows.microsoft.com/en-US/windows7/Open-the-Windows-Update-troubleshooter
An automatic troubleshooter is available that fixes some problems with Windows Update, and it might resolve this error for you
http://windows.microsoft.com/en-us/windows/troubleshoot-problems-installing-updates#1TC=windows-7
this error can appear when installing updates for Microsoft Office 2003,
to fix Windows update with error code:80070643:
http://windows.microsoft.com/en-us/windows/windows-update-error-80070643#1TC=windows-7
If your computers are in a domain environment and get updated by a WSUS server, I suggest to update the group policy with the command “gpupdate /force”.
Meanwhile, if it doesn’t help, please upload the Windowsupdate.log at: C:\Windows, this will give detail error information for further support.
Regards
Wade Liu
TechNet Community Support -
[Forum FAQ] Common steps to start troubleshooting Windows Update issues
In this article, we provide you some common steps to quickly narrow down Windows Update issues. Before you post your question, you can follow the steps below to see whether
the issue can be identified and resolved. If not, please post it in Windows 8/8.1 Forum with the analyzed details.
Scenario 1: New updates can’t be checked.
Make sure your internet connection works fine.
Make sure you could connect to Windows Update Server or Microsoft Update.
For more information about how to troubleshoot problems connecting to Windows Update or to Microsoft Update,
visit the following Microsoft Web site:
http://support.microsoft.com/kb/818018
Scenario 2: Windows Update can’t be installed or configured.
Suggestion 1: Run the
Windows Update Troubleshooter
Press
WINDOWS + X combination key to open the Control Panel;
Change its view by “Category”;
Click
Find and fix problems;
Under
System and Security entry, click Fix problems with Windows Update.
Follow the instruction to complete it.
Suggestion 2:
Make sure the following services could startup automatically
Press WINDOWS + R combination key, type “services.msc”, press
Enter;
Find out the following services and the dependent services:
Windows Update
Background Intelligent Transfer Service
Windows Modules Installer
Double click every service, on General tab, set its Startup type as “Automatic”;
Click Apply and OK button.
Note: If these services miss or damage, you need to use Windows 8/8.1 installation media restore them.
Suggestion 3:
Delete the Windows Update cache
Press
WINDOWS + R combination key, type “services.msc”, press
Enter;
Find out the
Windows Update service, right click and stop it;
Located to
C:\Windows\SoftwareDistribution;
Delete the whole
SoftwareDistribution folder.
Suggestion 4:
Reset the Windows Update component
For more information about how to
reset the Windows update component,
visit the following Microsoft Web site:
http://support.microsoft.com/kb/971058
Suggestion 5:
Install the Windows Update in a
Clean Boot state
For more information about How to perform a clean boot in Windows,
visit the following Microsoft Web site:
http://support.microsoft.com/kb/929135
Suggestion 6:
Reset, refresh or restore your PC, and then try to Windows Update
http://windows.microsoft.com/en-gb/windows-8/restore-refresh-reset-pc
Scenario 3: You might still be repeatedly offered the same update.
You need to check its installation status and decide if it should be installed again.
For more
information about Windows Update or Microsoft Update repeatedly offers the same update,
visit the following Microsoft Web site:
http://support.microsoft.com/kb/910339
Here are the solutions for some common Windows Update error codes or corresponding issues:
1. .NET Framework update installation error: "0x80070643" or "0x643"
http://support.microsoft.com/kb/976982
2. Error 0x800B0100 when you try to install Windows Updates or Microsoft Updates
http://support.microsoft.com/kb/956702/en-us
3. Error 0x80070005 in Windows Update when you try to install updates
http://support.microsoft.com/kb/968003/en-us
4. Error message 80246008
http://support.microsoft.com/kb/971058
5. Error message 80070003
Stop Windows Update service, rename SoftwareDistribution and catroot2 folder, then restart Windows Update service.
6. Error message 0x80072f8f
Check and correct PC’s Time and Date.
7. Automatic Windows update settings is gray out.
Please locate to the below registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU.
Add Value name: NoAutoUpdate
Value data: 0 or 1
0: Automatic Updates is enabled (default).
1: Automatic Updates is disabled.
Windows Store app update general troubleshooting steps
If you're unable to open the Store, try running the
Apps troubleshooter
If you can’t find the app update. Please consider these scenario:
Confirm if you set the proxy which affect the Windows store update.
For more information about using authenticated proxy servers together with Windows
8, visit the following Microsoft Web site:
http://support.microsoft.com/kb/2778122
Confirm the app is available in your current region;
Make sure “Automatically update my apps” is set to Yes;
Make sure the latest updates are installed on your PC and that your antivirus program isn't preventing the app from running.
Make sure the app isn't blocked by Windows Firewall
Sync your app licenses.
Try to clear
the Windows store cache on your PC:
Press
WINDOWS + R combination key, type “wsreset”, press
Enter;
Try to install the update again.
Applies to: Windows 8 and Windows 8.1
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.NEW
ADK download link is unavailable
https://dev.windows.com/en-US/featured/hardware/windows-10-hardware-preview-tools
Working one here at the bottom of the page -
How to throttle Windows Updates in BITS 4.0
Hi,
We are trying to solve a problem related to limiting the "Windows Update" traffic between Windows Clients and Internet Windows Update servers:
We have a WSUS infra setup like this:
Master server which is used for for approving patches, and managing computer groups. We don't store patches on that server, and clients are configured to download patches from the internet.
We have around 20 sites all sites are pointing "Intranet Update Server" to our master server.
The issue we are having is that in some cases, when we do a patch approval cycle, some remote sites with many users and insufficient internet bandwidth get lousy internet access performance.
We have identified the cause of this issue to be the large amounts of data that need to be downloaded by Windows Update.
The solution we are looking for is a way to limit Windows Update Traffic, so my mind jumped immediately to BITS.
I dug around the BITS features, and found the Peer Caching feature.
However as I read in Technet, BITS 3.0 has some peer caching capabilities.
With BITS 4.0 this has been removed, and the only caching available is via BranchCache.
I've read this thread(link), and
the OP is almost in the same situation as me, only he was trying to setup a branchcache server, and the clients would make use of that feature, when downloading from his internal WSUS.
So what are my options in terms of improving BITS bandwidth usage? Limit BITS download traffic during daytime hours?
p.s. Before someone says "Why don't you just setup a replica servers in each branch?" - we have no resources for this, and this doesn't play nice with many of our roaming users that go from location to location. Then we'll be moving our bandwidth
problem from the Internet lines to the MPLS/Leased lines - which are far more costly.
thank you,
ionutI dug around the BITS features, and found the Peer Caching feature.
However as I read in Technet, BITS 3.0 has some peer caching capabilities.
With BITS 4.0 this has been removed, and the only caching available is via BranchCache.
BranchCache is not an appropriate solution for your scenario, as it requires a WS2008R2 or later server to act as the server-based cache.
However, do not be confused by the fact that BranchCache and Peer Caching are enabled in the same way on a client system. PeerCaching is an appropriate solution for these sites.
So what are my options in terms of improving BITS bandwidth usage?
The starting place is to limit the background throughput utilization available to BITS. Almost certainly you're saturating the Internet link because each client is evaluating "available bandwidth" at the NIC, which even on a busy network would
still be 10+mbit/sec for each system.
The policies needed for this purpose are documented in the WSUS Technical Reference Guide:
Improve WSUS Download Performance with BITS. As described in the section "BITS bandwidth limitations", you'll need to set the policy "Limit the maximum network bandwidth for BITS background transfers".
But also in that section is the guidance on how to implement PeerCaching, which if all of your systems are BITS 3.0 capable, would be the best solution. In that case only *one* system downloads from Microsoft (it'll be the first one to detect the availability
of a new update, so you cannot predict or control this action), and the rest will get the needed files via LAN connections. Of course, you'll still want to limit the bandwidth utilization on the Internet link, and it will still need to be configured for ALL systems,
but it will be exponentially less utilization with PeerCaching than with everybody-for-themselves.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.
Maybe you are looking for
-
My 160Gb ipod can display some photos in fullscreen some cannot . What should I do to fix this prob?
-
2nd gen iPod touch only displays start-up apple icon, and is not recognized by iTunes - what to do?
2nd gen iPod touch only displays start-up apple icon, and is not recognized by iTunes - what to do?
-
Error: sim card inserted in this iphone does not appear to be supported.
Hi all-- Bought an iPhone 5 off ebay. It's totally wiped, and when I go to activate, I get a "Sim Not Valid" error on the phone, and "sim card inserted in this iphone does not appear to be supported" in iTunes. It is an AT&T phone, and has an AT&T si
-
Using collections and experiencing slow response
I am experiencing slow response when using htmldb_collection. I was hoping someone might point me in another direction or point to where the delay may be occurring. First a synopsis of what I am using these collections for. The main collections are u
-
hi all, 1.I have copied one exitsing code which has the creation of RoadMap component which has 4 items, only first one is getting highlighted. though i am able to traverse the other items are not gettting highlighted. 2.i have a button row whi