Windows 10: Announcing Windows 10 Insider Preview Build 14371 for PC

It's ok Kari. You know lots more than most of us about many more things, and you have been able to share what you know with everyone.

 

By the Gods I can hardly believe it...*Wink I deliberately left secure boot on for the install and to my utter amazement (exaggerating only a little) 14371 installed perfectly--as an upgrade install, no less--first time in many moons on my system...! Still, I did make my own ISO and upgraded in-place from that! (Lately the "flight" upgrade code coming through WU hasn't worked well for me--I suspect some kind of file corruption may be taking place through the upgrade/migration process.) But the ISO code seems to be working great, atm. My target system for Win10 Insider builds has about ~300 some applications and games installed over a few terabytes spanning several physical platter drives and SSD's--so doing a clean install every build is not my cup of tea, for obvious reasons!

 

Haven't been able to update to 14367 or 14371 (stops at 25% when installing). Thus I will need to get the ISO from a VM and do a clean install. This is not the most terrible thing in the world. On the other hand I could install Windows Server 2016 TP5 and just run 14371 in a VM. I could also install VMware WS amd ViruualBox image that and then uninstall those programs. Virtualbox can install in a Windows 2016 Hyper-V VM. It will only create 32-bit OS but that's fine. Of course 32-bit may not be supported by most distro's soon. I'm surprised MS has not abandoned it for Windows 10

 

Sleep seems to be broken in this build if you have "Save power when my device knows I'm away" enabled in power and sleep settings. If my tablet (Dell Venue 11 Pro 5130) has been asleep for a while, long enough for Windows to put it in deep sleep, then it hangs at the Dell logo when I try to wake it and I have to do a hard reset. Disabling the setting fixes the problem.

 

Tweet



— Twitter API (@user) date

 

I just checked and I don't have that option either.

 

Nope, not here, either.

 

Grrrrrrrrrrrrrrrrrrrrrrrr, it took out my Brother MFC-L2705DW. And after all that Simrick went through to get the blasted thing installed last week!

Sheesh, way to go, Microsoft!

And of course, the Feedback Hub seems to be broken. *Sad

 

Might it be because you are already signed in with MSA?

From the announcement yesterday:

 

Strange but the last two builds have removed CCleaner when I installed them.*Eek

 

Mine remain still.....in fact a reminder that a new update is available.

 

It certainly works for me.....with an M$ account...

 

Every new build since the beginning has removed CCleaner on my rig, also Speccy (also from Piriform).

 

It is ambiguous in my mind.

MS always said digital licences could be transferred to new mobo if like for like, but you had to get MS to do it if it failed to activate.

Also, an unresolved issue was if you could transfer windows 10 to a new mobo if you you originally upgraded from a retail 7/8 oem in free period, after free period ends (EULA certanly permits it).

According to EULA, you cannot transfer licence to a new mobo if you upgraded from an oem licence. Question is whether the new method can differentiate between retail or oem?

Perhaps MS have simply decided the number of people who replace a mobo is so small in reality, it is not worth the hassle checking original licence?

After all it is their vowed intent to get as many people using Windows 10, and being strict about oem licences is counter productive to that intent.

I will try an see if I can activate a vm this way.