I do the same process with success. (knock, knock). In a previous post I mentioned that I removed MWB Pro before I installed 16215, installed MWB Free afterewards. Should have nothing to do with the install, but then again, did not think MWB Pro was the reason for me not being able to save/save as anything from Word or Excel. Since then, my system is very responsive and fast.
I use no third party AV's or Firewall. MS says that Theirs is the best so that is what I use.
@f14tomcat
@Kari
I realize I'm an apprentice here and was taking a stab in the dark. I thought it be better than sit around doing nothing.
Here's a question > Logically if it loads on just one machine, it should load on all, unless, of course, system architecture comes in play or either UUP or ISO process gets corrupted at times, yes?
After bringing up the subject this morning and seeing the comments on it, it is leaning more towards system architecture rather that software interference. And it seems to be in the initial loading process, also.
Anyone know how many machines and OEMs/MoBo types MS would test installs on? Surely they must have labs for that, yes? OEMs as well?
I noticed this morning my lappy downloaded and notified me that it's ready for upgrade. It's on WiFi, whereas my tower is wired. I'm about to see what happens when I start the process.
@Al Airone
Your not the only one who doesn't use all but the Windows Defender. I haven't run anti-virus software in over 12 years. I simply know where I can go, where I shouldn't go, what is okay to download and what not to download :) I have not ONCE been infected by a virus or anything other than 'crapware' apps that install alongside a freeware app because I forgot to choose 'Custom' or Advanced install or forgot to uncheck the box for one of those 'helper' programs....which are easy to un-install.
If your Internet savvy and have something a lot don't have these days (common sense), then you should be okay for most part. That's not to say something won't happen of course.
I also download everything on my Linux boxes and use the Win10 machine strictly for gaming and absolutely nothing else.
While some would say I am gambling or putting my PC at risk; well....possibly. My chances (based on my past record) of getting into a car accident are higher than getting any virus. LOL.
Tim
ARS N9NU
I don't use my laptop much except for videos (mostly Netflix docs) to fall asleep with since I don't have TV service.
I postponed the UUP update process for 3 days this morning.
Started WU process (after initializing update in background I assume): 7:23pm
First restart: 7:39pm
"Working on updates" at 15%: 7:55pm
Attachment 139231
Tony,
I have no hard evidence, and nothing to link to, but I have a suspicion about the rollback at the 30% mark.
In the past, I seem to recall that's where it loads some drivers, graphics comes to mind, and maybe others...then re-boots to pick up the process. A missing/corrupt/inappropriate HDD/SSD driver could easily explain why the message "Inaccessible boot device". It can't find it, see it.
Let me explain some experience concerning MS installs and device drivers. I have a NVMe SSD drive on this system. It's in a eSATA slot, not SATA 0. If I go to do a clean install from a thumb drive, properly prepared with the MS ISO, it will fail to see what we would call "drive 0". Sees all others, not the first one, the NVMe SSD. In order to get it to see the drive, I have to include the Intel drivers for that SSD on the thumb, and load them manually. Then it will see the "C" drive and allow me to choose where to install.
I'm using that as an example of a missing driver in a MS official ISO installation package causing issues with the process. The same exact problem when using Kyhi's Rescue media. I have to "Inject" those drivers into his package (the part that comes from the official MS ADK) in the .wim file on the thumb, then when I boot his Rescue thumb, all the progs will see the "C" drive. If I don't', the drive is invisible.
I'm only using all of this as a basis for saying that this build package may be missing a critical piece, and causing the failure. It can also explain why updating a VM went smoothly and without any of these "boot" problems. In a VM, the boot process is controlled by the VM host, not Windows.
Again, I have nothing hard to post to prove any of this, just what I have experienced.
I would not say you are gambling at all. Myself and others in my computer club only use Windows Defender, MalwareBytes, and CCleaner. We all have had similar experiences as yourself with regard to malicious infections. Ransome ware? Not a worry - that's what a good backup plan is for! And, if all hell broke loose for whatever reason, I'll be "back up" and running in about 20 minutes.
Happy computing,
Rich
Quote
