Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider
-
Welp - I have no idea why, but it went stupid on the install, so I rebooted and it got back to the main Windows install of 199. I then attempted to use the .ISO t upgrade but upon loading it click the Install button just made the window go away and come back, it would not proceed. I then tried to use the .ISO via USB boot, and it gave me an error about some VCRedist executable file terminating abruptly. I chose my KB layout, an then it offered to let me boot, troubleshoot, or shut down. I shut down, and then when I powered it on, it started updating itself and went all the way through.
Sheesh.
-
-
Welp - I have no idea why, but it went stupid on the install, so I rebooted and it got back to the main Windows install of 199. I then attempted to use the .ISO t upgrade but upon loading it click the Install button just made the window go away and come back, it would not proceed. I then tried to use the .ISO via USB boot, and it gave me an error about some VCRedist executable file terminating abruptly. I chose my KB layout, an then it offered to let me boot, troubleshoot, or shut down. I shut down, and then when I powered it on, it started updating itself and went all the way through.
Sheesh.
This one is one weird build. I went back to 199 on all 3 machines, then reinstalled all 3. Corrected one problem on two computers - people program still missing on all 3. I'm through for today.
-
I think we can probably dub 215 as the buggiest upgrade yet. I can't believe they didn't test this on multiboot systems.
Whew! After reading about all the problems people were having, I expected the worst, but the upgrade to 16215 took place smoothly in about 1-1/2 hours. Just starting to give it a road test.
Upon checking to see if backup to network drive was still present, I noticed this information:
I'd never heard of it, although it appears to be something previously discovered:
Microsoft may be killing File History with the Windows 10 Fall Creators Update | Windows Central
If this is maintained into the next public build, I'll have to search out new backup software.
-
Do you mutiboot by any chance. I've been getting the same well now I guess we call it GSOD. Green screen of death
Yup, I multiboot three different versions of Linux and got the GSOD twice upon first reboot. However, this was only the second build that I had to revert to a clean install. This was the first time I used @Kari's UUPToISO procedure to create the ISO DVD and was up and running in 25 minutes. Some time ago I had created a Powershell script to install my usual 8-10 programs automatically - again @Kari had helped me with the use of Powershell. It really makes a clean install pretty painless.
Rich
-
-
Well, this is the furthest I’ve gotten with the install. Now at 51%. If you’ve got Acronis True Image 11 and Disk Director 12 installed, try uninstalling them, restart, and retry updating..
-
Whew! After reading about all the problems people were having, I expected the worst, but the upgrade to 16215 took place smoothly in about 1-1/2 hours. Just starting to give it a road test.
Upon checking to see if backup to network drive was still present, I noticed this information:
I'd never heard of it, although it appears to be something previously discovered:
Microsoft may be killing File History with the Windows 10 Fall Creators Update | Windows Central
If this is maintained into the next public build, I'll have to search out new backup software.
Look no further.
New Macrium Reflect Update
Most of us never use the native backup software.
-
Installing now from a clean install from the "official" Microsoft Insider 16193 ISO. It will be using the Microsoft Bootloader (dual boot with Windows Server 2016). I will get GRUB going after I install Hyper-V and WSL. This will work but its annoying.
-
-
Whew! After reading about all the problems people were having, I expected the worst, but the upgrade to 16215 took place smoothly in about 1-1/2 hours. Just starting to give it a road test.
Upon checking to see if backup to network drive was still present, I noticed this information:
I'd never heard of it, although it appears to be something previously discovered:
Microsoft may be killing File History with the Windows 10 Fall Creators Update | Windows Central
If this is maintained into the next public build, I'll have to search out new backup software.
I read about this at Paul Thurrott's site. I also read about how they are moving Cortana into the Action Center....
-
-
Hey, well done!!
- don't forget the Feedback Hub..
Quote
