New
#90
An X in the top right corner would be nice.
I have tremendous respect for your obvious knowledge 'n experience with PCs, however unless I'm mistaken (it wouldn't be the first time), I think you may have missed one step in diagnosing your machine that has boot failure during setup. As a last resort, OS install while Internet is totally disconnected should not fail with basic drivers, and would blow my mind if unsuccessful. If after you verify all that I'm saying it ends up being wrong, at least I tried to help. Just let me know.
"WU errors" mostly end up being false assumptions, and my experience shows the worst problem is the auto-install of improper graphics drivers by WU, which btw inherently could never be perfect at that task for the myriad of older devices. Subsequently, the statement that I question most is that "Windows found all the appropriate drivers..." and I'm not even familiar with the machine in question. I'd bet those drivers are different than what the manufacturer recommends for that specific AMD graphics model. Again, if my premise is erroneous please say so.
Following are links to your 2 posts on this issue, and ASH8's description of how offline installs can make the difference on older PCs, plus to my July 18 article...
jimbo45 - Fast 17735 - Aug. 10 (p6 #54) here;
jimbo45 - Skip 18214 - Aug. 10, (p9 #84) here;
ASH8 - Skip 18204 - July 25 (p10 #91) here;
OutsiderLarry - Fast [Slow] 17713 - July 11 [July 26] (p21 #203) here.
Stay cool...or should I say, Icelandic!
OK Doan. No more predictions. Buildfeed seems to be ex post-facto. Myabe we will get something maybe not.
But I have updated to a Gigabyte Aorus X470 Ultra Gaming MB with a Ryzen 7 2700X Processor and 32 GB of DDR4 RAM. I'll be working on mutlboot system - debating on whether to install Tumbleweed instead of resurrecting Debian Unstable.
For most Windows installs/upgrades this is absolutely correct. But lately there has been a lot of issues that have had absolutely nothing to do with driver incompatibility but rather bugs in Windows itself that causes very unpredictable behavior on same hardware. Windows PE barely runs and sometimes not at all. Same goes for Safemode.
These bugs occur both on physical hardware and any type of VM or emulator for specific builds, and I'm surprised how on some computers these issues occur while on others they don't. The only common changing factor between all these physical and virtual computers I can think of is the CPU itself.
Now when I really think about this, could it be that there is some code in Windows that tries to run 512bit AVX instructions or similar on CPUs that don't have such capabilities? That would explain some of the crashes.
More news about the upcoming Sticky Notes update for insiders in Skip ahead, dark theme.