Yes mate ever since the release of the RS-4s and not being able to upgrade or fresh install, I always make a UPP to ISO just before restart now, then make a bootable USB/ DVD with Rufus or ISO2Disc so I can try every possible way to upgrade or install
I’m going to try the tutorial in the morning
Thanks
I followed the instructions to the letter and for a while when all the RS-4 files were copied to the hard disk, I really thought this was going to work but unfortunately when I rebooted the system it was back to the same result.
Frozen on the windows logo with no spinning dots
I would appreciate more suggestions, I’m stuck.
Why are those 549 MB partitions assigned drive letters?
Even if you try to tell it to install to a larger partition / drive, with those two being assigned C: and D: you might be causing it to fumble during install....
Just making sure that the image you applied successfully was to F:, since I cannot read it in the penultimate image ? -the code used was:
dism /Apply-Image /ImageFile:E:\Sources\install.wim /index:1 /ApplyDir:F:\
F: had 278GB total in Diskpart and after applying the image has 290,507,005,592 bytes free?
Did you run the BCDBOOT f:\windows command?
There are 2 system reserved partitions, which of these is active - the other should be deleted, as it is redundant.
It is possible to have a drive letter assigned to the system partition, its just not very useful, as there's not much to see or modify in there, so often it is hidden, i.e. not assigned a drive letter. Probably safer too.
It is also possible to have System, Active, Boot, Pagefile, Crashdump &c. all in a single partition.
It's also not mandatory to have the Windows volume with a C: drive assignation either, just conventional. Now that floppy drives are generally obsolete, it's possible to use the A: & B: drives too - the floppy controller may need to be disabled in Device manager tho.
Yes mate it was from E to F, E (17040) being the source to install from and F the source to install to.
And yes I did run the BCDBOOT f:\windows command
After I rebooted and the system froze on windows logo, I tried it again and this time I did I to F.
I (16299) being the source to install from and F the source to install to and it works fine as it always has done with any RS-3s
The other system reserved partition is on a 1 terabyte drive which I’m using as a temporary backup of important files
Last edited by bordi; 07 Dec 2017 at 12:06.
I made a right mess of that last post I’ve edited it now it’s ok
Wintel seems to have scuppered the board for further upgrades.
My system two Acer Travelmate cannot progress beyond rs-2, in rs-3 and rs-4, the PNP is fouled up, so no base devices work, except the basic graphics driver, Upgrades fail, but it still clean installs (and DISM apply) and runs up to 17046 (and runs acceptably fast, considering the low specs) - just with no network, sound, etc, and these devices all need to be disabled which makes it fairly useless. On rs-2, it works fine, just a conflict with a couple of unsupported devices, which may be disabled. Here again though, the problems stem from lack of updated Intel driver support.
Just read this. Although it says no .ISO based installs are affected, I wonder if this DOES extend to UUP2ISO created ISOs?
Insider Preview Build Installs Fail with Error Code 80096004 - Microsoft Community
Bordi, have you tried an .ISO from the slow ring downloaded directly from Microsoft at all?
Quote