Server 2016 - Update issues preventing .NET downloads
- Thread starter A7tech
- Start date
Please attempt to update again with Process Monitor running.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the capture icon (CTRL +E) 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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the capture icon (CTRL +E) 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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.
How big is the zipped file?
Please try Internxt Send – Securely Send Large Files for Free with an 5GB limit
Or Fast & Simple File Transfers with 6GB limit
Please try Internxt Send – Securely Send Large Files for Free with an 5GB limit
Or Fast & Simple File Transfers with 6GB limit
Disregard, I must have highlighted the wrong thing. I was able to get the file uploaded to Wetransfer:
Logfile.zip
Logfile.zip
Hi,
Please open an elevated prompt, run the following command and post the result.
Please open an elevated prompt, run the following command and post the result.
Code:
fsutil resource setautoreset true C:\Hi,
Great, please run also the following command in an elevated prompt and post the result.
Great, please run also the following command in an elevated prompt and post the result.
Code:
fsutil transaction listThat looks promising, so please do the following first.
Download
ListChkdskResult.exe and save it on your desktop.
- Click the Start button and in the search box, type Command Prompt
- When you see Command Prompt on the list, right-click on it and select Run as administrator.
- When command prompt opens, copy and paste the following command into it, press enter afterwards.
Code:chkdsk - Wait for this to complete.
Download
- Rightclick ListChkdskResult.exe and select Run as administrator.
- Notepad will open the file ListChkdskResult.txt on completion. (This logfile ListChkdskResult.txt is also saved on your desktop.)
- Post the logfile ListChkdskResult.txt as attachment in your next reply.
Please run the following DISM command again to see if it still fails with error: 6801. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthPlease run the DISM command again with Process Monitor running.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run DISM again just like you have in the past.
3. Stop Process Monitor a minute or two after DISM failed. You can simply do this by clicking the capture icon (CTRL +E) 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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run DISM again just like you have in the past.
3. Stop Process Monitor a minute or two after DISM failed. You can simply do this by clicking the capture icon (CTRL +E) 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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.
Please run the following fix.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Afterwards reboot the server and run the following DISM command again! If it fails attach a new copy of the CBS log.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
- Save any work you have open, and close all programs.
- Download the attachment SFCFix.zip and save it to your desktop.
- Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Post the logfile (SFCFix.txt) as attachment in your next reply.
Step 2. Afterwards reboot the server and run the following DISM command again! If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthHmm, which (third party) security software is running on this server?
Has Sysnative Forums helped you? Please consider donating to help us support the site!