Upgrade to 1803 version fails with 0xc1900101-0x30017 error

So, is it safe to delete the LUMSYS driver because I'm not sure what needs to be uninstalled to remove it.

edit: I will take care of the chkdsk part

Reason has support.
Please communicate with them to see if they have an uninstall tool to remove any residual software or software fragments:
How do I uninstall Reason Core Security? - Support - Reason Core Security

Sure. I don't want to take up anymore of your time until I'm ready with the results. Your time's much appreciated.

Hi. This error was received on all of my machines that had 3rd party AV.
On removal of AV the installation was successful.

up to 17666 (rs5) no antivirus was able to be installed as on reboot, the system would hang with gsod.
getting into safe mode and uninstalling the AV was the only way to run that version.

currently updating to 17672 and will try again, but not hopeful.

R

BundyBob said:

Hi. This error was received on all of my machines that had 3rd party AV.
On removal of AV the installation was successful.

Sadly, no such luck here

Run HD Sentinel: (free edition)
Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance

How old is the computer?
Which parts are not original/replaced?


Pending the results of HD Sentinel you can use Windows driver verifier.

For Windows driver verifier there are 3 methods to turn off or recover from using the tool.
All methods are using the Windows advanced troubleshooting menu.
The methods should be performed in order, moving to the next method only if the prior method fails to turn off the tool.
1) Startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type:
verifier /reset
2) command prompt > Administrator: X:\Windows\System32\cmd.exe > X:\Sources > type:
verifier /bootmode resetonbootfail
3) system restore
When using system restore the dump files are often lost. If the dump files are lost there is little progress made in the troubleshooting. So it should be the last option to recover from using the tool.

The tool will be used for 48 hours. After the last BSOD it will be used for an additional 36 hours of typical computer use.

When using the tool the computer may become sluggish and boot may become slow. If there are significant problems the test customizations can be modified.

Use the test setting in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Use this link for methods to turn off or recover from using the tool:
Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials

After each BSOD > post a new BETA log zip into the thread

Make sure that you have a Macrium backup and a brand new restore point before using the tool.

The System's roughly 7 years old. All parts are original though I've done a few upgrades (RAM and Hard disk). I also had the motherboard changed with an OEM replacement some two years ago. The old one had some Gpu related issue. Everything's been working fine since the replacement.

Do you see anything wrong with the hard disk because of the temp related failure notification. I personally haven't noticed a drop in performance or anything indicative of a possible issue. As for the temps 50deg is pedestrian here in the tropics. The temps (disk) hover around mid to high forties even during the winter months and it's summer time here now.

For slow performance problems you may not notice them over time.
For acute performance problems you will notice them.
The benchmark transfer rate is slow. There was high CPU usage.
So if you are considering replacing the drive you can take care of the failure to upgrade, temperature, and transfer rate problems simultaneously. In addition you could consider an SSD to get faster boots and better performance.

Run the Crucial scanner to get a general idea of drives available:
Crucial System Scanner | Crucial.com

2) command prompt > Administrator: X:\Windows\System32\cmd.exe > X:\Sources > type:
verifier /bootmode resetonbootfail

This is to typed into an admin CMD when logged in I presume?

The tool will be used for 48 hours.

Does this mean the system will be in the driver verifier state for full 48 hours or can I stop after a BSOD. It's not very clear to me.

If there are significant problems the test customizations can be modified.

You mean I have to redo the verifier by picking only the three options (as suggested in the link below ) as opposed to all but two.

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

So if you are considering replacing the drive you can take care of the failure to upgrade, temperature, and transfer rate problems simultaneously. In addition you could consider an SSD to get faster boots and better performance.

Does this imply the upgrade failure is somehow tied to degrading disk performance? Honestly, I didn't have any plans of a Disk upgrade...A new disk may improve performance but there's bound to be little effect on the temps unless the disk manufacturers have made a significant leap in cooling...It's a naturally warm/hot ambience where I live. Moreover, the disk temps have been consistently in that range, give or take 5 deg, since the day I got it.

edit: I'll check that out