bigbearjedi … what kind of severe problems?
an update happened to me thursday evening as i got home … the yellow-screen and throbber … appeared as i attempted to "restart" my laptop. this screen lasted well through the night. two hours after it's inception, i crawled into bed (left computer on) … that update seemed to have finished 3:10am. at 4:45am, i got outta' bed … noted the computer was in desktop mode … promptly shut her down.
arrived home 1pm that afternoon (friday) … microsoft was telling me the upgrade failed … not enough space in the partition. performed some theatrics in the admin-tools … and found another 18gb free-space. smooth sailing after that … the yellow-screen again present … successfully integrated au's latest release (14393.187).
w10 is feeling happy once again … and i am feeling disgruntled (as always).
p.s. thanks for the continuing updates on w10-au … gives an old fart bit of confidence … or, perhaps, tolerance.
>>>Hi Jack:
Here's the post with what happened on my laptop:
============================================================================================================
Well, I knew it was too good to be true! September AU update came into my W10 Sony Vaio laptop this morning around 2AM, and I let it run. It removed 2 apps from my pre-AU configuration (CCleaner & 8Gadgetpack), and made me remove my Norton Internet Security and update to the latest Norton I.S. version and then completed the update. It was all looking good, I even made a post on here on the main AU thread. Then Norton had me reboot, and wham! I suddenly lost like 15 keys on my keyboard that were no longer working correctly!
I tried several things, including full chkdsk and sfc. No go there. I tried some other repairs as well; no luck. Tried booting in Safe Mode too; but the problem persisted. I was getting ready to Restore from a Macrium Image Backup to my pre-AU config, and I thought I'd try the new "ROLL BACK TO THE PREVIOUS BUILD". I've never done the rollback before and it's now in the Advanced Options=Recovery menu. It worked!
I'm disappointed that there is some problem with my laptop and the latest September AU build,
v1607 b14393.187. It could be the keyboard or human interface drivers, I didn't check the Dell website to see if they had a later version than what the W10 AU installed. But, I'll get back to that later. I'm going to wait on letting that update into the laptop until October and see what that update does. In the meantime, I'm going to let the update into my other 4-W10 machines and see if they have a similar problem. They have different hardware, cpu's, Mobos, etc.
Back to the drawing board Microsoft...
At least the September AU update finally came into one of my computers through Windows Update and self-installed.
I'll report back further developments here..stay tuned!
BBJ
============================================================================================================
Glad you like what I'm attempting to do.
As you are well aware, not everyone out there is as comfortable as we are about borking a working W10 system, backing it all up to external media, doing a Clean Install of the W10 OS, reinstalling
ALL their programs and data, not an easy task for most folks, just to get to the next level.
That's why several of us on the W10 Insider Community are posting to the Hub and telling Microsoft that they should call the AU update what it is;
W10.1 or maybe
W10.2; and be done with it.
MS certainly didn't have any problems calling the big rollup update in W8 --> W8.1 did they? And if you played around with that update, it didn't go in nice either.
I had to do problably a dozen of those on Customer machines. The last update that went in smoothly (on a clean running windows machine of course!) was SP1 on W7 (W7-->W7 SP1).
I gotta go paint my house some more...
EDIT: If you could put a
"Like" on my Post here, that would be helpful to let other people know my efforts are appreciated on this topic! Thanks!
Have a good one.
BBJ