well you may spend 8 hours a day with this stuff and it is all pretty clear to you. but come to my workplace and you will feel like an idiot when you have no education in thermodynamics. i want an 1809 enterprise installation medium ready to put on an USB stick. that´s it.... too much to ask here? instead everyone needs to download first an old version and then convert it into an actual version with a tool?
The tool thread has an OP, like on this thread's OP, that one gives all info needed, the tool downloads 17763.1 and 17763.107 Techbench Consumer ISO's and 17763.1 All MVS iso's.
Hi all I have Amd Gigabyte GA-MA790FXT-UD5P Processor : And Phenom 2 X 4 955 Ram : 4x4 = 16 Gb SSD :250 I changed My bios setting to OnChip SATA Type : AHCI OnChip SATA Port4/5 Type : As SATA Type Onboard SATA/IDE Ctrl Mode : AHCI I have downloaded windows 10 Enterprise 64 bit version 1809 After installing on my ssd I enabled From program features Hyper-V It needs a restart after restarting My windows doesn't open It show windows boot screen and restart again and going through diagnosing I tried many times to repair it doesn't work I reinstall Windows again many times No way when I enable Hyper-V Please help Thanks
difference ? Win10_1809Oct_English_x64 SHA1: bee211937f3ed11606590b541b2f5b97237ac09d en_windows_10_business_edition_version_1809_updated_sept_2018_arm64_dvd_3edd051e.iso SHA1: 50e60954a073dc1383c494054e14f0d69387e397
1. the sha-1 2. Win10_1809Oct_English_x64 is TB/MVS consumer ISO 3. en_windows_10_business_edition_version_1809_updated_sept_2018_arm64_dvd_3edd051e.iso is MVS/VLSC Business iso. Content Consumer ISO's: [01] 10/30/2018 en-US 10.0.17763.107 Windows 10 Home | Core [02] 10/30/2018 en-US 10.0.17763.107 Windows 10 Home N | CoreN [03] 10/30/2018 en-US 10.0.17763.107 Windows 10 CoreSingleLanguage | CoreSingleLanguage [03] 10/30/2018 en-US 10.0.17763.107 Windows 10 Education | Education [04] 10/30/2018 en-US 10.0.17763.107 Windows 10 Education N | EducationN [05] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro | Professional [06] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro N | ProfessionalN [07] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro Education | ProfessionalEducation [08] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro Education N | ProfessionalEducationN [09] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro for Workstations | ProfessionalWorkstation [10] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro N for Workstations | ProfessionalWorkstationN Content Business ISO's: [01] 10/30/2018 en-US 10.0.17763.107 Windows 10 Education | Education [02] 10/30/2018 en-US 10.0.17763.107 Windows 10 Education N | EducationN [03] 10/30/2018 en-US 10.0.17763.107 Windows 10 Enterprise | Enterprise [04] 10/30/2018 en-US 10.0.17763.107 Windows 10 Enterprise N | EnterpriseN [05] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro | Professional [06] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro N | ProfessionalN [07] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro Education | ProfessionalEducation [08] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro Education N | ProfessionalEducationN [09] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro for Workstations | ProfessionalWorkstation [10] 10/30/2018 en-US 10.0.17763.107 Windows 10 Pro N for Workstations | ProfessionalWorkstationN [11] 10/30/2018 en-US 10.0.17763.107 Windows 10 Enterprise for Virtual Desktops | ServerRdsh
so both are the same build ? only difference in license [volume/retail] ? which is better for me "already my Microsoft email linked with activation"
HWID = OEMRET but on a VL install you can easily insert the HWID generic key to enable the HWID activation (on previously established hwid activated system).
All iso's released on MVS: https://forums.mydigitallife.net/th...-17763-1-107-pc-r.77945/page-191#post-1483804
They are still named September Update, because MSFT decided to replace the 17763.1 september update with iso's with almost the same filename But they all are oct. refresh iso's Btw, the fod lp's and ondemands, still are 17763.1, the new windows 1809 refresh iso's are just updated with an older CU, no new compiled build.
Make sure virtualization features of the CPU aren't disabled in BIOS. Still the age of the CPU might be the culprit here, not sure if it supports all Hyper-V hardware requirements .