ex_bubblehead - Yes, I have viewed, studied, and tried everything (or almost everything) on each of the links. For example:
- I have not only turned off all antivirus programs, but have removed them. (Avast in particular)
- Turned off the firewall
- Incompatible driver - as noted, I went through the computer and disabled everything I could, one by one, running the update each time to see if removing that one would fix it. Did not help.
- tried installing it over both wireless and cable. As suggested, disabled the wireless card. Not only that, but I also created a USB disc, and disconnected all internet access, and tried running it that way. Did not help.
- removed every USB device, except when I disabled the touchpad on the laptop, I had to keep the usb mouse plugged in.
- ran sfc/scannow - ran it several times, especially after messing with the register as required by some of the links
- updated everything from Windows (except this current update) and updated BIOS to current version. Even tried some of the automatic driver upgrade programs but all I got was a load of viruses on my machine that I had to clean off.
- of course, before doing this, I ran Avast complete scan, and then clean files and cleaned the register with CCleaner.
- did not run the log and send separate file to Microsoft, since everytime I get the BSOD, it sends out the logs (or at least it says id does)
The above was everything on your first link.
For your second line:
- did everything in the quick fixes. Removed everything from the computed. I have no personal files left on it at all and removed all programs other than windows.
- I could not run setupdiag.exe - I have NET Framework 4.7 installed. Article says I need 4.6 and I guess that is why setupdiag.exe would not run.
- Troubleshooting - good info, but all it got me was that my error is occurring in the First Boot Phase
- error logs - spent some time trying to decipher these. There is one for each time I tried to load the upgrade. Per your note, they all have "Panther" in them somewhere. Some were not accessible. Not sure why. Bottom line is that there were a lot of error codes and they were not consistent. The last one had 0xC1800104 and several instances of -x800705BB. One before that was zero bytes. One before that had one error code of 0x000000b7 - failed to create Window PE rollback directory. I think this one had to do with the restore after the failure.
Note that the DC WATCHDOG VIOLATION did not show up in an error log but was shown on the BSOD message. That is the one that got me looking on the Microsoft site to see what it meant and led me to chasing down the AHCI issue and the lack of such choice on this laptop
The last item on your second link was to submit all this to Microsoft. I have not had good results in doing that, but prefer to submit it here or on MajorGeeks.
Your third link - this one dealt exclusively with the Ox30018 error code. It was good, but I have done every task mentioned there, including all the ones which are the same as in the first link you sent, plus disabling sound adapters in BIOS, running the DISM tool, using Media Creation to create the USB and running the upgrade from the USB, running the pnpclean registry hotfix. However, I did not try the registry key creation and modification they discussed. Just too much messing around in the registry, especially since I don't know how these would react with the other registry fixes.
So. No. I have ignored your advice (or I should say the advice given in the links you provided).
My last post was directed at the BSOD reference, which I had not seen before, and the discovery that AHCI could not be activated on this laptop. Trying to find out if others have had the same issue.