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

Hello - Will share the update soon, DISM command was ran by another team mate, so he will let me know.

If you are available - opening another thread, let me know if you can check for similar issue, thank you
 
Yes, he was actually the one who suggested I reach out to you here. He had already said so many great things about you, which are absolutely true and honestly, you’re even more amazing than he described!


By the way, under C:\Users, there are currently 28 profiles.
 
Sure, but he is no more working on these issues or with this project itself.

And let me know when can we work on the server issue
 
Also, adding the component scanner file - Resuly:
ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows Server 2016 Standard x64 (10.0.14393.8066)
Start time: 2025-07-07T08:59:53
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 186970
Number of values: 509638

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None


Storing 0KB in C:\Users\Adm1n\AppData\Local\Sysnative\ComponentsScanner

Finish Time: 2025-07-07T09:09:09. Corruption scan time: 516.9705664s
===========================EOF===========================


Thank you
 

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

Back
Top