T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 3, 2019 #1 We are running Windows Server 2008 r2 sp1. we are trying to install windows management framework 3.0, and it fails with Catastrophic failure - error 2147549183 everytime We have ran the System Update Readiness Tool and SFC /scannow completed with no errors. we also ran windows update and it completed successfully. the other thing that gave us an error was SFC Fix which said "Failed to check for updates. This may be due to an internet connection problem or a temporary availability failure of the update servers. Please ensure you are using the latest version of the program before continuing or exit now..." Our goal is to update Power shell 2.0 to at least 3.0. But the error 2147549183 is holding us back while trying to install KB2506143-x64. Also, we did update to Windows .NET Framework 4.7.2 and enabled Windows PowerShell ISE Any help would be appreciated!! View attachment CBS - log.zip View attachment CheckSUR.log
We are running Windows Server 2008 r2 sp1. we are trying to install windows management framework 3.0, and it fails with Catastrophic failure - error 2147549183 everytime We have ran the System Update Readiness Tool and SFC /scannow completed with no errors. we also ran windows update and it completed successfully. the other thing that gave us an error was SFC Fix which said "Failed to check for updates. This may be due to an internet connection problem or a temporary availability failure of the update servers. Please ensure you are using the latest version of the program before continuing or exit now..." Our goal is to update Power shell 2.0 to at least 3.0. But the error 2147549183 is holding us back while trying to install KB2506143-x64. Also, we did update to Windows .NET Framework 4.7.2 and enabled Windows PowerShell ISE Any help would be appreciated!! View attachment CBS - log.zip View attachment CheckSUR.log
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 4, 2019 #2 got sfcfix to run here is the result: SFCFix version 3.0.1.0 by niemiro. Start time: 2019-01-04 09:33:38.868 Microsoft Windows Server 2008 R2 Service Pack 1 - amd64 Not using a script file. AutoAnalysis:: SUMMARY: No corruptions were detected. AutoAnalysis:: directive completed successfully. Successfully processed all directives. Failed to generate a complete zip file. Upload aborted. SFCFix version 3.0.1.0 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2019-01-04 09:39:01.884 ----------------------EOF-----------------------
got sfcfix to run here is the result: SFCFix version 3.0.1.0 by niemiro. Start time: 2019-01-04 09:33:38.868 Microsoft Windows Server 2008 R2 Service Pack 1 - amd64 Not using a script file. AutoAnalysis:: SUMMARY: No corruptions were detected. AutoAnalysis:: directive completed successfully. Successfully processed all directives. Failed to generate a complete zip file. Upload aborted. SFCFix version 3.0.1.0 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2019-01-04 09:39:01.884 ----------------------EOF-----------------------
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 6, 2019 #3 Hello and welcome! Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try installing the update just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and attach the LogFile.PML file as well as your CBS.log
Hello and welcome! Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try installing the update just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and attach the LogFile.PML file as well as your CBS.log
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 8, 2019 #4 Hey, here is the link to the files - LogFile.zip Thank you!
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 9, 2019 #5 Is the following key present: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{e7ef96be-969f-414f-97d7-3ddb7b558ccc}
Is the following key present: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{e7ef96be-969f-414f-97d7-3ddb7b558ccc}
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 9, 2019 #6 yes it is. here is a screen shot of it https://www.screencast.com/t/UixBs8Hk
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 9, 2019 #7 Please export it somewhere, then delete it from your registry, reboot and retry the WMF 3.0 install.
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 9, 2019 #8 We tried to install Windows6.1-KB2506143-x64.msu again and it failed. should we try to run process monitor during the install and post the results again?
We tried to install Windows6.1-KB2506143-x64.msu again and it failed. should we try to run process monitor during the install and post the results again?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 9, 2019 #9 Step#1 - FRST Scan 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Right click to run as administrator. When the tool opens click Yes to disclaimer. 3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already). 4. Press Scan button. 5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop) 6. Please attach the log back here. 7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
Step#1 - FRST Scan 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Right click to run as administrator. When the tool opens click Yes to disclaimer. 3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already). 4. Press Scan button. 5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop) 6. Please attach the log back here. 7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 10, 2019 #10 Here are the documents after running FRST tool. i removed the accounts from the Addition.txt file for security reasons. let me know if it is needed. View attachment Addition.txt View attachment FRST.txt
Here are the documents after running FRST tool. i removed the accounts from the Addition.txt file for security reasons. let me know if it is needed. View attachment Addition.txt View attachment FRST.txt
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 15, 2019 #11 Sorry for the delay. Is the following update installed: KB3020369
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 15, 2019 #12 Good Morning. Thank you for replying, but that update is currently not installed.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 15, 2019 #13 Please install it and retry installing WMF afterwards. Make sure you reboot the system prior to attempting WMF.
Please install it and retry installing WMF afterwards. Make sure you reboot the system prior to attempting WMF.
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 15, 2019 #14 We have installed the KB3020369 package and the KB2506143 right after. Failed with the same error
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 15, 2019 #15 Can I see CBS.log and setupapi.dev.log? Please confirm that you have rebooted the Server after installing KB3020369.
Can I see CBS.log and setupapi.dev.log? Please confirm that you have rebooted the Server after installing KB3020369.
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 15, 2019 #16 Yes i did restart the computer. here are the log files View attachment Log Files.zip
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 18, 2019 #17 Do you have the latest Servicing Stack Update installed?
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 18, 2019 #18 We've run the windows update tool and completed all updates to date. If the servicing stack is a part of those updates, then it should be "up to date". If not, we will have to find the standalone updates to get the servicing stack to the latest versions. We have found this link. should we install the standalone and retry wmf? Download Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932) from Official Microsoft Download Center
We've run the windows update tool and completed all updates to date. If the servicing stack is a part of those updates, then it should be "up to date". If not, we will have to find the standalone updates to get the servicing stack to the latest versions. We have found this link. should we install the standalone and retry wmf? Download Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932) from Official Microsoft Download Center
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 18, 2019 #19 This is the update I am talking about: http://download.windowsupdate.com/d..._42467e48b4cfeb44112d819f50b0557d4f9bbb2f.msu
This is the update I am talking about: http://download.windowsupdate.com/d..._42467e48b4cfeb44112d819f50b0557d4f9bbb2f.msu
T tient4290 Member Joined Jan 3, 2019 Posts 11 Jan 18, 2019 #20 hmm, we installed that update package and it was successful, then we rebooted the system and tried to install WMF which was unsuccessful. But, do you think we should scrap the 2008 and migrate to 2016??
hmm, we installed that update package and it was successful, then we rebooted the system and tried to install WMF which was unsuccessful. But, do you think we should scrap the 2008 and migrate to 2016??