There are three different PC models here, all configured in the same way, all have to have Windows Updates installed on them automatically. However, while two of the models were happily updated, the third decided it does not like some of the updates and presented me with the screen similar to the following:
Turns out these two error codes are quite known problems.
The first one is solved, among some other options, by downloading and installing a specific update: , which is over 300MB in size. So in my case I had to do a check for the PC model by reading it via PowerShell
$strModel = (Get-WmiObject Win32_ComputerSystem).Model.Trim()
and if the model was the "weird" one, install this update.
The second one is solved by repairing the .NET Framework 4 installation. Fortunately, this can be done either silently or with unattended option. All in all, the fix for my two problems was applied as the following addition to the script and, fortunately, no additional restarts were required and after running this bit I could proceed to install updates as per my previous post.
if($strModel -Like "*WeirdModel*") { Write-Host "Verifying .NET Framework 4 ..." Start-Process "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe" "/repair /x86 /x64 /ia64 /parameterfolder Client /passive /norestart" -Wait Write-Host "Done." Write-Host "Installing System Update Readiness Tool ..." $readinessTool = Join-Path $win7Folder "Windows6.1-KB947821-v27-x64.msu" $toolCommand = $readinessTool + " /quiet /norestart" Write-Host $toolCommand Start-Process "wusa.exe" $toolCommand -Wait Write-Host "Done." }
References:
Error Code 0x80073712 occurs in Windows Update or Microsoft UpdateSystem Update Readiness Tool for Windows 7 (KB947821) [May 2013]
Error codes “0x80070643” or “0x643” occur when you install the .NET Framework updates
Silent install, repair and uninstall command lines for each version of the .NET Framework
by Evgeny. Also posted on my website
No comments:
Post a Comment