New
#190
Unbelievable, just as we speak 14332 is coming down the pipes on my spare drive with 10586 on it. Everything going well I'll be able to update 14316 once I make an ISO.
Announcing Windows 10 Insider Preview Build 14332 for PC and Mobile Insider
-
-
New #191
I could not upgrade `14316 to either 14328 or 14332 - stuck at 25% of install everytime. What I did is make a clean install of 1511 in a VM (in my case VMware WS 12.1.1 - but it should work in Virtualbox as well). Windows 10 VM was offered both updates immediately. The install ESDtoISO and create the ISO inside the VM. Copy the ISO to an external USB or CD-ROM and then burn you ISO. That's a clean install of 14332. Now I have quite a few programs that I have re-install (68 or so). But I've saved the programs to an external and those that I bought saved the keys on Gmail or Dropbox. Doesn't take much time to reinstall everything (you will probably find some programs you actually don't want).
-
New #192
Very similar to what happened to me, and also my solution, except that I didnt have the VM. The other fhing is, I'll be upgrading from the ISO not clean installing, I've got too much stuff to do a clean install. I could have done that from day one if I didnt have 130gb of games.
-
New #193
I think you may want to start a separate thread for that in order to be able to go over things more fully. Could be a need to reseat a card if not a hardware if not software related problem. Dust buildup can be a cause for problems at times!I sure hope there's a new build soon..
I got this glitch during install of 14332 (see the GFX anomaly onscreen) - it froze at this point:
Attachment 77539
- after about 20 mins of inactivity, I hit the restart button..
- sorry 'bout the screenie, but I'm just too frazzled to rotate it
- AMD graphics have been completely haywire ever since..
- 90% of webpages won't load correctly..
- Fallout4 and many of the latest games wont function correctly
- Quantum Break fails to run at all, as do several Steam titles
- I've given my hardware a good once over and there aren't any faults that I can see
- I have to assume a buggy install of 14332 is the culprit
Any type of beta build is only expected to see a very short life span to begin with. The 90 days are the typical allotted evaluation time for just about any MS as well as other software product. A non activated Windows would see the 28day time frame. By then even the Slow ring will have seen another newer build go on as the rule of thought there.
-
New #194
Has anyone ever updated a preview to a later preview from an ISO without losing their settings and programmes, I'm just getting a bit nervous about doing this. I dont know if the ISO is like the online update and smart enough to know not to wipe stuff.
Im going from 14316 to 14332 and 14332 is an ISO.
-
New #195
This is encouraging, because it is an attempt to get WER to run in Win PE, right from the very beginning of setup. Encouraging because of all the failed clean installs that might never be analysed otherwise. I am hoping that there is somewhere the crashdumps from incidents like this are saved to be sent once there is enough of a system to "phone home" with the relevant crash data, although in this case, it would seem unlikely that there was time enough for that to happen. It repeated, you say, so maybe there's hope.
I rarely see BSODs, but I have been getting reproducible BSODs on build 14332 recently whenever I try to run VMs in Virtualbox. The disappointing (but understandable) thing is the length of time that the BSOD takes to gather all the data and then restart the machine, and worse, the lack of indication that anything is happening (apart from a very sluggish %age indicator) once the unsmiley logo hits the screen. The QR code was unhelpful when I caught it on my phone. I'll be sending a BSOD report to TF later today.
I am sure that my reaction in the past has been to just force a power down and reboot, rather than to wait for WER to do its stuff. It seems logical that users would want to move on from an error state as soon as possible, and not stare at a blue screen.
Because the general conception is that BSODs are a "bad" thing, rather than a very useful tool for MS to analyse and improve the behaviour of Windows when things go wrong, it would seem that BSODs need to have their image polished, and have more information on screen about what is going on, why and approximately how things are progressing as WER completes its tasks.
When error statesseemed to bewere much commoner in early XP days for instance, and user permission to send error data back to MS was asked for on screen it didn't seem to take very long at all, but I guess those were mostly appcrashes, rather than system ones.
-
New #196
I can tell you how I was able to get the 332 on a VM lately when it wouldn't arrive by way of the updates during a recording of the entire upgrade from the previous 328 build which instead turned out to be a no go on the upgade by updates but a complete clean install from the BT folder! The first of two 7 to 10 VM upgrade projects was where that was seen having extracted the entire BT folder from another Pro VM to the 7 Pro to TH2 upgrade which had been updated as far as the 328. The upgrade path was listed as incorrect when the outside of WU upgrade was attempted forcing the clean install. The second 7 Ulitmate VM on the other hand was left running and 12hrs. later following that VM's TH2 upgrade saw the 322 downloading and go on without a hitch.
If you are planning an iso install expect that to also run into the clean install situation as your only option. The build to build carry over only works by way of the Windows Update function and not from any other method. This is how things are geared to work especially with the changes being seen lately.
-
New #197
-
New #198
-
-
New #199
The upgrade option was also present on the VM when manually starting the 10 installer by clicking on the setup.exe file as if you were manually clicking on the same being on removable media. The BT was on a separate partition seen when expanding the vhd. And iso install would be seen by the VM's main setting while any physical upgrade operates without a host OS running in the background being the difference when the physical machine restarts. The VM test was to determine what options are available from a BT folder install. Didn't look good for any repair installs when not having any other media available!
Quote
Related Discussions
