What versions are included in Microsoft Tool? I downloaded the ISO and used it to upgrade my Enterprise edition and it did!, system details says it is Enterprise and kept KMS activation. I thougt it only included Home and Pro.
At the OP the content of the ESD's is published, the ESD's is what the MCT downloads for ISO creation.
With 1803 MS finished the licensing switch between virtual editions. If one installs Professional (or ProWork/ProEdu/Edu) it actually installs Enterprise with the GPO activated for Professional. Advantage of this is the ability to use the Pro ISO to upgrade all higher edition installs via In-Place-Upgrade. Actually a useful move.
I reply to my enquiry with an update. I was trying to synchronise against WSUS on 2016 patched to date and there was a cached entry for a timer sometime in the future and for some reason, I couldn't make Windows 10 17134.5 scan now. The timer value is in the WindowsUpdate.log retrieved with the Powershell command Get-WindowsUpdateLog, run as administrator. I made it working after changing a Group Policy setting the scanning frequency to 1 hour and repeatedly running usoclient startscan. It is one of those things experienced by the earliest adopters on all new installs. Probably with some patience, this would have fixed itself once the timer value expired. Windows 10 17134.5 Enterprise here, installed from ESD made in ISO and upgraded in place over 17131.73, previously upgraded in place over 1709, whatever latest version (CU) was available at the time.
So all you need for an in place upgrade to 1803 of "any version", is the Microsoft Tool downloaded from MS? I'm Asking just to get it clear for other users.
Hey all, I have an older system I've built and have been using for about 8+ years now. Yes, it's old but fits my needs for the time being. This is what I have: Asus Rampage III Extreme Motherboard Intel 780X i7 Extreme CPU 16GB DDR3 RAM Dual Nvidia GTX 580 SLI Dual Samsung 512GB 830 series SSD Four mechanical Western Digital HDs (2 @ 2GB & 2 @ 4GB) Tri-monitor setup As you can see, it was not a bad setup in the old days. Just haven't felt the need to upgrade since I have current laptops and tablets that are only a few years old. Anyways, if you have family, you can understand. The problem I am having is installing a clean version of Windows 10 Pro, April 2018 Update. Installation will freeze at the Windows 10 Logo when booting. I'm booting off a usb drive and when the system starts, it would sit at the Windows Logo for several minutes (about 4-6 mins). At this time, there is a lot of disk activity but only the logo will display, no animation. After a while it would just sit there and freeze; no disk activity after this (disk led goes out). Only way to get the system working again is to reboot by holding the system power button down until it powers off. Now, I've had this similar problem with All version of Windows 10 Update installation (Redstone 1 - Redstone 3; Redstone 4, being the April 2018 Update). In the past, the system would wait at the Windows Logo (with disk activity as describe above), but setup would continue once the 4-6 mins pass and installation goes through smoothly. Not this time. I've even re-installed Window 10 1709 (Fall Creator's Update from last fall, Redstone 3) and though it would seem to hang at the Windows Logo upon initial boot, setup continues after several minutes. Now the only drive I have connected to the system when installing windows is the boot drive (one of the 512GB Samsung SSD), all the other drives won't be reconnected until setup is finish and working. That's how I did in the past since Windows likes to shift the drive orders around. Anyways, I've even tried upgrading to from Windows 1709 to 1803 using the DVD copy of Windows I got from the Windows creation tool... and same results. When the system reboots, it hangs at the Window Logo. I was even able to get the system to download the 1803 update from Microsoft vai Update... system hangs at the Windows Logo when booting. There was one time that I was able to get an error messaging after attempting to upgrade from Windows 1709 to 1803, that was: We couldn't install Windows 10 We've set your PC back to the way it was right before you started installing Windows 10. 0xC1900101-0x20017 The installation failed in the SAFE_OS phase with an error during BOOT operation Anyone having similar issues or know of a way to fix this? Thanks.
Not really, this time MSFT didn't open the gates to them (yet), people like @GezoeSloog and other people who have access to MVS, luckily share all files
Added x86 business svf and svfsfx patches: https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324/page-112#post-1432280
I would check your system first. - Run Memtest86 on those rams for a couple of hours - check SMART status of all your hard-drives (reallocated sector count and pending sector count needs to be 0) - update system bios, disable any overclock - Disable one of the gpu's, all hard disks - If all fails, use winpe and winntsetup OR other computer to install the image on your boot ssd