Windows Server 2012 update 2019 error (0xC1900101-0x20017)

[BlueSky]

Hi all,

I need your expertise.


My server is running Windows server 2012, and the following failures occurred during the upgrade to 2019:

0xC1900101-0x20017
During the SAFE OS phase of the BOOT operation, the installation failed with an error



This is the troubleshooting log made before installation

OneDrive:computerinfo.txt ,ipconfig.txt and systeminfo.txt
windows server 2012.rar

The following is the check log file after the installation failed


OneDrive：setupact.log and setuperr.log
setup.rar


After that, I ran the following command to check:

sfc/scannow
Dism/Online/Cleanup-Image/ScanHealth
Dism/Online/Cleanup-Image/RestoreHealth

OneDrive：CBS.log
CBS (1).rar

Thanks for your help.

 

[BlueSky]

update :

I have followed the steps (Windows Update Forum Posting Instructions).
And the results of these one are there : File -Microsoft OneDrive
In the shared folders, you can find :
- "file1.rar"
-include:CBS folder,components.txt,sfcfix.txt,dism.log

 

[PeterJ]

Hello and welcome,

Download & Run the tool SetupDiag

1. Open the website SetupDiag Download Page
2. Click the Download SetupDiag button.
3. Create a new folder on your Desktop and nove the file SetupDiag.exe to that folder.
4. Right-click the "SetupDiag.exe" and click Run as administrator.
5. When completed, three files are created, "Log.zip," "SetupDiag.exe.config," and "SetupDiagResults.log" in the folder SetupDiag.exe was executed.
6. Attach only the file "SetupDiagResults.log" to your next reply.

 

[BlueSky]

Dear PeterJ,

The following is the content of SetupDiagResults.log, thank you


Matching Profile found: FindRollbackFailure - 3A43C9B5-05B3-4F7C-A955-88F991BB5A48
SetupDiag version: 1.7.0.0
System Information:
Machine Name = BJBIMFILE01
Manufacturer = VMware, Inc.
Model = VMware Virtual Platform
HostOSArchitecture = x64
FirmwareType = PCAT
BiosReleaseDate = 20180703000000.000000+000
BiosVendor = PhoenixBIOS 4.0 Release 6.0
BiosVersion = 6.00
HostOSVersion = 6.3.9600
HostOSBuildString = 9600.21620.amd64fre.winblue_ltsb_escrow.230929-1158
TargetOSBuildString = 10.0.17763.107 (rs5_release_svc_prod2.181026-1406)
HostOSLanguageId = 2052
HostOSEdition = ServerStandard
RegisteredAV =
FilterDrivers = luafv
UpgradeStartTime = 2024/3/22 16:42:19
UpgradeEndTime = 2024/3/22 17:32:49
UpgradeElapsedTime = 00:50:30
RollbackStartTime = 2024/3/22 17:42:58
RollbackEndTime = 2024/3/22 17:45:59
RollbackElapsedTime = 00:03:01
CV = 8IcAgZcoekeWEDGW


Error: 0xc1900101-0x20017 SetupDiag reports rollback failure found.
Last Phase = Finalize
Last Operation = Remove System Restore checkpoints
Error = 0xC1900101-0x20017
LogEntry:

Refer to "Tutorial - Debug system error codes - Win32 apps" for error information.

Last Setup Phase:
Phase Name: Finalize
Phase Started: 2024/3/22 17:32:35
Phase Ended: 2024/3/22 17:32:42
Phase Time Delta: 00:00:07
Completed Successfully? True


Last Setup Operation:
Operation Name: Remove System Restore checkpoints
Operation Started: 2024/3/22 17:32:42
Operation Ended: 2024/3/22 17:32:42
Operation Time Delta: 0:00:00:00.0000000
Completed Successfully? True

 

[PeterJ]

ChkDsk Scan

• Right-click the Start button and click Commandprompt (Run as administrator).
• A window appears. Typ CHKDSK and press the enter key.
• Wait until CHKDSK is finished.
  
• Download ListChkdskResult.exe by SleepyDude and save it on your desktop.
• Rightclick
  
  ListChkdskResult.exe and click Run as administrator. On completion the tool will save a textfile called ListChkdskResult.txt on your desktop.
• Attach this text file to your next reply.

 

[BlueSky]

Dear PeterJ，

The following is the content of ListChkdskResult.txt, thank you

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

------< Log generate on 2024/3/28 8:59:00 >------
Category: 0
Computer Name: Bjbimfile01.nwsebj.nwse
Event Code: 26212
Record Number: 146368
Source Name: Chkdsk
Time Written: 03-28-2024 @ 00:50:17
Event Type: 信息
User:
Message: 在卷快照上以只读模式执行了 Chkdsk。

检查 C: 上的文件系统
文件系统的类型是 NTFS。

警告! 未指定 F 参数
在只读模式下运行 CHKDSK。

阶段 1: 检查基本文件系统结构...


已处理 772096 个文件记录。
文件验证完成。


已处理 39129 个大型文件记录。


已处理 0 个错误的文件记录。

阶段 2: 检查文件名链接...


已处理 911736 个索引项。
索引验证完成。


已扫描到 0 个未索引文件。


已恢复 0 个未索引文件。

阶段 3: 检查安全描述符...
安全描述符验证完成。


已处理 69821 个数据文件。
CHKDSK 正在验证 Usn 日志...


已处理 545116304 个 USN 字节。
Usn 日志验证完成。

Windows 已扫描文件系统并且没有发现问题。
无需采取进一步操作。

总共有 163480575 KB 磁盘空间。
384483 个文件中有 65171512 KB。
69822 个索引 270792 KB。
坏扇区 0 KB。
系统正在使用 1381239 KB。
日志文件占用了 65536 KB。
磁盘上 96657032 KB 可用。

每个分配单元中有 4096 字节。
磁盘上共有 40870143 个分配单元。
磁盘上有 24164258 个可用的分配单元。

-----------------------------------------------------------------------

 

[PeterJ]

Perform following scan.

FRST Scan:

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
   64-bit: Downloading Farbar Recovery Scan Tool
   Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
   
   
2. Note: Rename the downloaded file FRST64.exe to English.exe.
3. Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
4. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
5. Press the Scan button.
6. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
7. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.

 

[BlueSky]

Dear PeterJ，

The attachment below contains Addition.txt and FRST.txt, thank you

 

[PeterJ]

I have 2 questions first.

a)Do you still have this printer in use ?
Oray PrintProcessor

b) There are some remnants of antivirus programs present. Are the following antivirus programs uninstalled ?
Qihoo 360 Antivirus
Symantec Endpoint Protection
Kaspersky Lab

 

[BlueSky]

Dear PeterJ，

Oray PrintProcessor not use ;

The following antivirus programs uninstalled:
Qihoo 360 Antivirus
Symantec Endpoint Protection
Kaspersky Lab

 

[PeterJ]

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on English.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[BlueSky]

Dear PeterJ，

The attachment below contains Fixlog.txt, thank you

 

[PeterJ]

Great.
Try the upgrade again and report the result.

 

[BlueSky]

Dear PeterJ，

Still the following fault prompt appears

 

[PeterJ]

Attach the files $Windows.~BT\Sources\Rollback\setupact.log and $Windows.~BT\Sources\Rollback\setupapi.dev.log to your next reply.

 

[BlueSky]

Dear PeterJ，

not found setupapi.dev.log,There is a folder named setupapi which I put inside the zip package,Thank You.

 

[BlueSky]

Dear PeterJ，

not found setupapi.dev.log ,setupact.log uploaded;
A folder named setupapi has been uploaded after compression. It contains three log files starting with setupapi. I'm not sure if this is what you need. Thank you!

 

[PeterJ]

FRST Scan:

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on English.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[BlueSky]

Dear PeterJ,

The content of the Fixlog.txt file is as follows:

Thank you.


Fix result of Farbar Recovery Scan Tool (x64) Version: 02.04.2024
Ran by zhangqing (20-04-2024 10:32:23) Run:2
Running from C:\Users\zhangqing\Desktop\420
Loaded Profiles: zhangqing
Boot Mode: Normal
==============================================

fixlist content:
*****************
Folder: C:\Windows\System32\DriverStore\FileRepository\lsi_sas3.inf_amd64_cce8c19de27c79ab
Folder: C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3
*****************


========================= Folder: C:\Windows\System32\DriverStore\FileRepository\lsi_sas3.inf_amd64_cce8c19de27c79ab ========================

2015-07-07 15:04 - 2014-05-28 19:31 - 000042261 ____A [06AD9BF2D47C8257DC754BAA3A5A8946] () C:\Windows\System32\DriverStore\FileRepository\lsi_sas3.inf_amd64_cce8c19de27c79ab\DriverConfigParam.def
2015-07-07 15:04 - 2014-06-24 00:30 - 000017327 ____A [8D047D2A7639B0B337DCF032C1B347D3] () C:\Windows\System32\DriverStore\FileRepository\lsi_sas3.inf_amd64_cce8c19de27c79ab\LSI_SAS3.cat
2015-07-07 15:04 - 2014-06-02 19:56 - 000005322 ____A [29BD9D648160C6EE4C5A5D71E99D3E79] () C:\Windows\System32\DriverStore\FileRepository\lsi_sas3.inf_amd64_cce8c19de27c79ab\lsi_sas3.inf
2015-07-07 15:50 - 2015-07-07 15:50 - 000015140 ____A [130C4549417BA8BB71ABCC74C5972318] () C:\Windows\System32\DriverStore\FileRepository\lsi_sas3.inf_amd64_cce8c19de27c79ab\lsi_sas3.PNF
2015-07-07 15:04 - 2014-06-02 19:57 - 000084144 ____A [468CC15F7CC79F0E57B1BF0D1284BA5A] (LSI Corporation -> LSI Corporation) C:\Windows\System32\DriverStore\FileRepository\lsi_sas3.inf_amd64_cce8c19de27c79ab\lsi_sas3.sys
2015-07-07 15:04 - 2014-06-02 19:57 - 000159408 ____A [D2F8FA5A19AE5182F9D963BF862CDF97] (LSI Corporation -> ) C:\Windows\System32\DriverStore\FileRepository\lsi_sas3.inf_amd64_cce8c19de27c79ab\wdcfg.exe

====== End of Folder: ======


========================= Folder: C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3 ========================

2015-07-07 15:04 - 2014-08-01 10:07 - 000137728 ____A [163DB6105ABAFE4E8CC0219077867778] (Microsoft Windows Hardware Compatibility Publisher -> QLogic Corporation) C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3\nxancs.dll
2015-07-07 15:04 - 2014-08-01 10:10 - 000002939 ____A [60CD30EABDC9F18987837B7C98534055] () C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3\nxancsx64.inf
2015-07-07 15:50 - 2015-07-07 15:50 - 000009040 ____A [97A3DC69062B3F4E3E503E9A7D8D6481] () C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3\nxancsx64.PNF
2015-07-07 15:04 - 2014-08-01 09:26 - 000831346 ____A [6454F1FEAE2B35DD4C98A501B26F886D] () C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3\NxTeamingUiCHM.chm
2015-07-07 15:04 - 2014-08-01 10:10 - 003512832 ____A [5169F64DBE661D23EC2C9A2D231FEF7B] (Microsoft Windows Hardware Compatibility Publisher -> QLogic Corporation) C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3\qlCoTeam.dll
2015-07-07 15:04 - 2014-08-06 00:48 - 000020099 ____A [0B3EC4B039FDC42DB46E825A489698B5] () C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3\qlnd6x64.cat
2015-07-07 15:04 - 2014-04-04 03:02 - 000274432 ____A [AF3223567989DD372867736B7021CC68] (Microsoft Windows Hardware Compatibility Publisher -> QLogic Corporation) C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3\qlteamcli.dll
2015-07-07 15:04 - 2014-08-01 10:14 - 000651264 ____A [F3DDD710A2A5C318B2C14AB4FAFC840A] (Microsoft Windows Hardware Compatibility Publisher -> QLogic Corporation) C:\Windows\System32\DriverStore\FileRepository\nxancsx64.inf_amd64_e6073ac55e4ec0d3\qlxgnd64.sys

====== End of Folder: ======


==== End of Fixlog 10:32:23 ====

 

[PeterJ]

FRST Scan:

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on English.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.