Not able to take my windows server 2016 to windows server 2022.

I trust you with more then anyone when it comes to these issues.

I have added 100GBs - and now I have 167 GBs -

Will initiate now :)
 
Please be patient and check the free space, if it's not running out of space let it run, and I've seen cases where it can take more than 17 hours to complete.
 
Hi,

Okay, let's hope the system will not run out of free space this time.
 
Hi,

The error seems to be different now with an time-out issue.

1. Please run the following DISM command and copy paste the result in your next post.
Code:
DISM /online /cleanup-image /AnalyzeComponentStore


2. Download
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner and save it to your desktop.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 
Last edited:
I would suggest to cleanup the Components Store first, but make always a snapshot / backup before you run the following command just to be sure. And please note that this command will take some time to complete due to the number of reclaimable packages, so I would run it overnight when this server is not in production.

Code:
DISM /online /cleanup-image /StartComponentCleanup
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top