New
#500
@f14tomcat
Thanks for the info, TC. Did you ever find out why your new system drive configuration was set up the way it is?
I can see I may be burning the midnight oil here tonight.
My lappy on WiFi:
Like I said earlier, it downloaded the update overnight. I postponed the update process for 3 days this morning.
Started WU process: 7:23pm (after it initialized update in background I assume)
Reboot: 7:39pm (“Working on updates”)
Second reboot at 30%: 8:10pm
Third reboot at 33%: 8:13pm (reboot spinning, taking awhile)
Took 3 minutes for that reboot: 8:16 (33% sound familiar? Installing drivers?)
Now at 50%: 8:20pm
Fourth reboot at 75%: 8:27pm
Finished that process > Reboot: 8:43pm
“We’ve got some updates for your PC” > Blah, blah, blah > “Let’s start”: 8:46pm
That’s what?!! 1 hour 22 minutes? That’s quicker than previous updates for this lappy.
Now no Wifi. Ran troubleshooter. Says that WiFi adapter having problems, then this screen:
Attachment 139238
Hmm. No WiFi adapter driver?
I guess I'll sign off here and shut this rig down so I can plug my Ethernet cable into the lappy. Hopefully find a driver?
"Apology build" does sound good. I wonder if Dona will say anything about why the team released a build that they knew had numerous problems. Anyway I learned a bit about my backup and imaging solfware.
Yes and even that was iffy for a bit. I could see it kinda like flashing deciding what to do. Thinking it was loading a driver since I've never had this lappy plugged into Ethernet.
Here's shots of Device Manager and the card properties with a bunch of events. Says "Windows cannot initialize the device driver for this hardware. (Code 37)". Anyone know? Bad driver I assume?
Attachment 139240
Attachment 139241
Attachment 139242
Attachment 139243
Attachment 139244
No. It was not on upon final boot. It's the MS card driver. Do you have Ralink 802.11n Wireless Lan Card? Many in Feedback are reporting it broken.
Tried reloading the driver via the troubleshooter in Defender console. No go.
Going to try this next. Download Ralink* Wireless Network Driver for Desktop Boards
It's not "bad driver".
You can install a "good driver" to no avail on systems that have upgraded, with loss of WiFi.
Wifi just fails with this build for many systems.
Has anyone made the upgrade to 16215 where the WiFi does not fail?
If so, which adapter and driver continues working?
Has anyone attempted to upgrade from other builds than 16199 with any success on machines that have failed when attempting upgrade from 16199?
I feel that Microsoft knew there might have been problems, firstly because the long delay between 16199 and the release of 16215, and secondly because of the Canonical nature of the UUP upgrade type - in that it might not have not have been able to perform an Express (Differencing) upgrade.
I have to state that I have no machine yet that has not upgraded successfully.
On second thought, I don't use this lappy a whole lot and really have no business running IPs on it. Besides, I'm too busy having 2 machines with them. One is enough for testing. I have a CU ISO thumb that I'll fresh install with.