Hello.
Thanks all for your replies/insight.
I must apologize for not explaining clearly what is happening.
It's exactly the same scenario as CarlSD posted (Installation freezing at blue logo). What's baffling me is that v1803 works perfectly, but v1809 not (I would like to know whether v1809 introduced new features that made it that different from v1803).
PS - I have not tried the WU route. I may have just try that (just for fun).
Best regards.
Mostly likely a driver issue... find the older driver and injecting it into the 1809 wim may help.
Had a similar issue installing Ubuntu, fortunately it let me know in no uncertain terms it did not like the GPU - so could take remedial steps.
Hi there
I have to disagree -- latest windows 1809 (normal via WU not via insider releases) actually seems to work just fine whether on a VM (running on CENTOS 7 Linux HOST) or on a Windows laptop. Even Networking is behaving - at least at the moment.
Mind you I don't run anything complicated on Windows -- usually just OFFICE / OUTLOOK / EXCEL/ POWERPOINT/PROJECT and a bit of photoshop. So no Games or eseoteric hardware. SKY GO needs Windows as well and I have a SAPGUI front end for logging on to corporate SAP back end systems (hosted on Linux / cloud - SAP HANA for example).
Surfing etc usually I do via Firefox on Linux so no probs with that either. Netflix and Amazon prime also work on Linux.
I've been disappointed though in the insider releases -- SANDBOX is essentially 100% useless and they still can't fix the problem of display language and welcome screen in other languages if you install these in addition to the primary language. To me fix those before piffling little things like whether or not cortan is integrated with search etc -- who uses cortana anyway -- if I want to scream at a computer then it's time for me IMO to be admitted to "The funny Farm" or certainly another session in the pub is called for.
Cheers
jimbo
I would think using Windows Update is the worst way to update your version.
With Windows Update you have to deal with everyone else in the world using it too.
Using the Iso file method is so much easier, and more reliable, in my opinion
But as you`ve said that won`t work either
Hi folks
ISO is the best way normally but on the whole if you don't have a load of stuff installed on Windows and no specialized hardware and not into gaming WU works reasonably well.
Why 1809 won't install on the OP's computer either via WU or ISO suggests there's some problem with hardware.
Personally I've found on whatever hardware I've got my hands on (and I've tried a load !!) Windows will always install from clean - even if a lot of drivers are missing -- OK VGA (640 X 480) doesn't look very pretty on a large monitor !! but once you've got base windows installed then WU can usually find drivers etc.
Check also whether UEFI or BIOS for boot device - if UEFI you need to create an efi partition (formatted fat32) on the target install HDD. Creating a bootable USB from a downloaded iso using rufus is the best bet -then windows install will do it all automatically.
Cheers
jimbo
Minor update:
I think Superfly is totally right because the installation just hangs up upon starting. I suspect VGA driver. Now I must find out a way on how to inject drivers into a wim/iso.
I updated its old bios but it did nothing.
V1809 isn't offered on WU either.
Another option.... swap the boot.wim of 1803 with that of 1809.
Otherwise:
Export from current system all of your driver files to a new folder on your desktop ..
Then this to inject: https://community.ivanti.com/docs/DOC-29823:Code:dism /online /export-driver /destination:C:\Users\eLPuSHeR\Desktop\I_hate_1809_drivers
If all goes well, Windows update will then come along and overwrite them...and back to square one ... LOL
Thanks Superfly. I did the drivers thing yesterday but to no avail. I think it hangs so fast it doesn't even start loading drivers. I will try swapping boot.wim just for fun.
Best regards.
Another update:
Swapping BOOT.WIM files makes the installation to launch but it won't proceed. It's telling me some driver is missing (USB, hard disk, whatever). I tried from usb and from dvd (and with injected drivers version). No dice. I am now trying the swapped version from inside w10 v1803
Quote
- even low level drivers can change from build to build, so when you think there might be no possible problem, there could be with the next build.
