Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider

Page 51 of 98 FirstFirst ... 41495051525361 ... LastLast

  1. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #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?
      My Computers


  2. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #501

    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?
      My Computers


  3. Posts : 2,491
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #502

    "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.
      My Computers


  4. Posts : 29,078
    Windows 10 21H1 Build 19043.1023
       #503

    HippsieGypsie said:
    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?
    That's exactly what happened to mine, Hippsie, except it didn't tell me to plug in an Ethernet cable. It just said it couldn't figure out what was wrong.

    So, did the Ethernet cable work for you?
      My Computer


  5. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #504

    Wynona said:
    That's exactly what happened to mine, Hippsie, except it didn't tell me to plug in an Ethernet cable. It just said it couldn't figure out what was wrong.

    So, did the Ethernet cable work for you?
    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
      My Computers


  6. Posts : 29,078
    Windows 10 21H1 Build 19043.1023
       #505

    HippsieGypsie said:
    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?
    Did you turn off WiFi, Hippsie?
      My Computer


  7. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #506

    Wynona said:
    Did you turn off WiFi, Hippsie?
    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
      My Computers


  8. Posts : 1,983
    Windows 10 x86 14383 Insider Pro and Core 10240
       #507

    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.
      My Computers


  9. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #508

    Fafhrd said:
    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?
    Thanks for that, Chris. Yes, I finally figured that out since it still states "Windows cannot initialize the device driver for this hardware. (Code 37)".

    Might have to simply roll back and go with slow ring on this machine. There may be an update soon too.
      My Computers


  10. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #509

    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.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:07.
Find Us




Windows 10 Forums