Update Version 1803 to 1809 Consistently Gets Error 0xc1900101

No joy with the iso on BD-R. I booted from it and it said to reboot Windows and run setup instead. I did that and got error 0xC1900101 - 0x30018 on the first reboot. Microsoft says that happens when "A device driver has stopped responding to setup.exe during the upgrade process." Suggested remedy is "Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display. Contact your hardware vendor to obtain updated device drivers. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process."

This is the first time I got the secondary error code, 0x30018, so that's something.

I once had a problem with something on USB (probably a RAID on USB) that prevented boot after a BIOS update because it thought something weird was the boot device. Solved it by unplugging all USB ports for that first boot.

- - - Updated - - -

One thing I didn't mention - I'm running on an Aten KVMA switch. The BIOS recognizes the keyboard and mouse through it so I'll leave it in for the next attempt, but all the USB plugs come out except the KVMA connection. If that gets the driver lockup, I'll go direct and try again.

Will try this afternoon, using the BD-R Windows 10 v1903 installation disk.

Besides unplugging all usb devices and disabling AV's, try disconnecting the 2nd drive, the data drive. Windows may be confused as to where to place the installation, a big reason 1903 won't even install, in most cases, from a usb stick.
You can also copy the files from your BD-R disc to your desktop and run setup.exe from there, after r-click/Mount to take out another variable.
Also, if you have nothing else on the C drive other than Windows, it would be easy to install and 'Keep nothing'. Windows would install generic drivers vs trying to use an incompatible one and you can deal with those later. Good Luck

The second HD is inside the box on a SATA cable, and has identical hardware to that of the system HD. It's a big job, physically, to disassemble the main box. Of course, it's a bit of a job to climb under the desk and unplug the USB cables, too...

I can mount the ISO file and run setup from that, but I think I'll stay with the Blu-Ray disk for the first try on the off chance that the upgrade host can have better luck with the partitions if it's not hosted on the system drive. I could move the iso file to the 2nd HD... so many possibilities.

I have vast amounts of software on my system drive. I would love to do a clean install with a repartition, but this isn't feasible. I would forgo the upgrade first. And, my next OS would likely be Debian/KDE, not Windows. But I am not letting a bad driver push me around. When I find it, it will go, even if it means a new RAID enclosure or whatever.

I've already gone through all the drivers available on Hardware Manager. There was one USB driver that it upgraded.

More this afternoon, after I unplug all the USB cables and try again.

There are log collectors that are used in another forum.
Please run both V2 and DM log collectors and upload results into this thread:
BSOD - Posting Instructions

Uh, OK. Here.

I'll give things a few minutes before I start pulling apart my USB network.

1) The computer has been having BSOD: 5/25, 5/21, 5/20

2) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

3) Make a new restore point:
Create System Restore Point in Windows 10


4) Update the Acronis backup image

5) Read these links on windows driver verifier: (do not use the tool until it is communicated in the thread)
(learn the methods to use the windows advanced troubleshooting menu to turn off and recover from using the tool)
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

6) Open administrative command prompt and type or copy and paste:
7) sfc /scannow
8) dism /online /cleanup-image /restorehealth
9) chkdsk /scan
10) wmic recoveros set autoreboot = false
11) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

12) Make sure that there is no over clocking while troubleshooting.

I think the BSODs reported in the logs are the events that stopped the upgrades. BSODs are very rare on this computer and I haven't had one in awhile. But this is important: the driver problems in the update process are BSOD-level events.

The requested Advanced System Settings windows:
Attachment 235051Attachment 235052

I created a restore point before my last update attempt from the Blu-Ray disk last night that should do.

Just started Arconis backup. Will make fresh Acronis boot DVD when it's done. I'll also copy time-critical files to my other computers.

I run sfc and dism occasionally just for luck. I do a chkdsk on all drives less often. The wmic command is new to me. The results of running these sequentially, as requested:

Microsoft Windows [Version 10.0.17134.766]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc.exe /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism.exe /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.766

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is <Redacted for privacy>.

Stage 1: Examining basic file system structure ...
1304064 file records processed.
File verification completed.
32248 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
39490 reparse records processed.
1622482 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
39490 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
159210 data files processed.
CHKDSK is verifying Usn Journal...
40795864 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

1953280071 KB total disk space.
1196023204 KB in 967667 files.
558620 KB in 159211 indexes.
0 KB in bad sectors.
1648527 KB in use by the system.
65536 KB occupied by the log file.
755049720 KB available on disk.

4096 bytes in each allocation unit.
488320017 total allocation units on disk.
188762430 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot=false
Updating property(s) of '\\8-CORE_WINDOWS\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>

I'll look at the material on Windows driver verification when all the checks finish. The full backup won't be done until this evening.

This machine is for serious work and it's no toy. I don't overclock, ever. In fact, the 16 GB of fast RAM is underclocked. It's rated at 1866 MHz and tested at that when new, but I let the Motherboard set the RAM clock at its default clock rates, more like 1400 MHz. It's 8 cores and 4 to 4.3 GHz is enough.

Motorfingers said:

I think the BSODs reported in the logs are the events that stopped the upgrades. BSODs are very rare on this computer and I haven't had one in awhile. But this is important: the driver problems in the update process are BSOD-level events.

The requested Advanced System Settings windows:
Attachment 235051Attachment 235052

The attachments did not work.

Please post new attachments.

There were older BSOD:

Code:

Event[26213]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2019-01-20T15:10:51.643
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: 8-Core_Windows
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffff988d31d8c7a0, 0x0000000000000000, 0xfffff803c95243cb, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 39d381fb-01d1-4bd6-a050-233e7c5fdf2d.

Code:

1/20/2019 8:11 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 50
P2: ffff988d31d8c7a0
P3: 0
P4: fffff803c95243cb
P5: 2
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\012019-47234-01.dmp
\\?\C:\WINDOWS\TEMP\WER-233421-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1D3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF251.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF31B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF35B.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_f048eabf6bc83b77af1eb05078e5b6aaa183722c_00000000_cab_0b93f677

Analysis symbol: 
Rechecking for solution: 0
Report Id: 39d381fb-01d1-4bd6-a050-233e7c5fdf2d
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
1/20/2019 8:11 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 50
P2: ffff988d31d8c7a0
P3: 0
P4: fffff803c95243cb
P5: 2
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\012019-47234-01.dmp
\\?\C:\WINDOWS\TEMP\WER-233421-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1D3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF251.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF31B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF35B.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_f048eabf6bc83b77af1eb05078e5b6aaa183722c_00000000_0303f379

Analysis symbol: 
Rechecking for solution: 0
Report Id: 39d381fb-01d1-4bd6-a050-233e7c5fdf2d
Report Status: 4
Hashed bucket: 
Cab Guid: 0

I noticed the problem with the attachments and am looking for them... OK, they are attachments now, the embed inline having failed.

For startup and recovery system failure
a) change kernel to automatic memory dump
b) reboot to maintain settings

Windows driver verifier can be started after:
a) making a new restore point
b) making sure the Acronis backup image is up to date
c) understanding the windows advanced troubleshooting commands to turn off or recover from using the tool
d) verifier: reset and/or bootmode commands should be used first and restore should be used only when the prior commands fail (system restore may cause the loss of the dump files and little progress is made in the troubleshooting)


Start windows driver verifier with the 3 customized settings in the Ten Forums link:
Enable and Disable Driver Verifier in Windows 10

The tool will be ran for 48 hours and then for an additional 36 hours after the last BSOD.
If there are no longer any BSOD that will complete the use of the tool.

During the testing the number of customized tests should be increased by 4 to 5 / hour to the 19 customized tests in the Microsoft link:
https://answers.microsoft.com/en-us/...3-c48669e4c983

While using the tool there may be performance problems and very slow boots.

You will have flexibility in adding and subtracting the customized tests. Ideally all non-Microsoft drivers will be exposed to the 19 customized tests.