Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider
-
Build 15222 working well on my mobile. It seems a lot smoother and faster than previous releases.
-
-
The WiFi issue affects 5y-old HP Compaq CQ57 Ralink RT5390 adapter on 16215 x86 - although it is reported as "Windows cannot initialise the device driver for this hardware. (Code 37)" in Device manager. Worked OK on 16199.
Feedback hub will not work on this build, when connected to internet via wired ethernet.
Attachment 138714
Odd...I tried it today and it works without a qualm (wired.) Last time I got your error, I simply went to Settings/Apps, found the Hub, and used the "Reset" option, and immediately connected. Hope you get it squared away!
-
In reading through many of the problem posts I see that trouble seems to be linked to the VM. I mentioned earlier that I had a refreshingly trouble-free upgrade install from 16199 to 16215, but I am on the hardware as opposed to virtual--and wondering why that might make a difference for people in upgrading to this build--if it does. It took about 30 minutes to download, which is only a bit longer than it usually takes, and the install time was the normal 30 minutes for me (as it is an upgrade, which always takes longer, but is nothing like the time it would take to install all of my applications and games every time...Yikes! That would take days!... Out of the question!) Just thought I'd pass along the info for comparative purposes in the hope that it might be a bit useful to someone.
-
OK, home again. I'm tempted to fix the issues, but I am just as tempted to do a clean install of CU and go from there. It's been a while, and I know I would feel better of a clean install anyway.
Decisions, decisions.....
-
-
In reading through many of the problem posts I see that trouble seems to be linked to the VM. I mentioned earlier that I had a
refreshingly trouble-free upgrade install from 16199 to 16215, but I am on the hardware as opposed to virtual--and wondering why that might make a difference for people in upgrading to this build--if it does. It took about 30 minutes to download, which is only a bit longer than it usually takes, and the install time was the normal 30 minutes for me (as it is an upgrade, which always takes longer, but is nothing like the time it would take to install all of my applications and games every time...Yikes! That would take days!...
Out of the question!) Just thought I'd pass along the info for comparative purposes in the hope that it might be a bit useful to someone.
Sorry to disappoint you... I'm on hardware and install failed with error. Finally succeeded with Windows update reset. That install was quick, but now I'm unable to run Edge (even reset didn't help - thanks for the suggestion Brink :)) and whole system feels somehow not as snappy as it was before.. see below, all critical events don't even fit in the screen..
-
Thanks for the suggestion @Brink. Forgot about that .. didn't work, thou. I'm running sfc at the moment and will reset Windows afterwards.
-
In reading through many of the problem posts I see that trouble seems to be linked to the VM. I mentioned earlier that I had a
refreshingly trouble-free upgrade install from 16199 to 16215, but I am on the hardware as opposed to virtual--and wondering why that might make a difference for people in upgrading to this build--if it does. It took about 30 minutes to download, which is only a bit longer than it usually takes, and the install time was the normal 30 minutes for me (as it is an upgrade, which always takes longer, but is nothing like the time it would take to install all of my applications and games every time...Yikes! That would take days!...
Out of the question!) Just thought I'd pass along the info for comparative purposes in the hope that it might be a bit useful to someone.
Nope - this is my physical hardware that is giving me fits.
-
Odd...I tried it today and it works without a qualm (wired.) Last time I got your error, I simply went to Settings/Apps, found the Hub, and used the "Reset" option, and immediately connected. Hope you get it squared away!
I reset the Hub and it is now working, thanks.
-
Remember to run
chkdsk (chkdsk /f if there are errors)
sfc /scannow
If either or these two come up with errors and are not fixed, you WILL go through the entire update sequence and then at the last gasp revert back to the last build! You can do it before or you can do it after. Why do I always end up doing it after? I tell you...
Ran chkdsk, no errors.
Ran sfc, no integrity violations.
And yet this build refuses to get installed.
Looks like I am clean installing....
-
-
Did that, still didn't work.