hi guys i am running windows 10 ent x64 bit build 10240 kmspico activated , can i update it to windows 10 creators edition , if so kindly share the link to an enterprise 64bit version of it
Yesterday I restored a (legally activated) Win10 x86 partition w/ build 14393 (using WHS2011), it wouldn't boot or show-up on the boot menu so I took a Build 15063 x86 DVD & did a clean install, no problems at all, shows up on boot menu... all is good. I checked settings/activation after a restart & it is activated, as was the broken W10 build I had before. The new MB has a dual BIOS & I have had problems restoring any working backups... so far.
I downloaded your VL ESD file (Education VL x64 en-us), converted it to ISO, and tried to create an SFV from x64 multiple edition MSDN iso. I am unable to obtain a reasonable sized SFV file, the difference file obtained is nearly same size as the whole ISO (more than 3 GB), when generlly this kind of SFV is around 40megs. Any explanation to that , please ?
Did you use option 1? i don't know for sure, maybe because wimlib introduce slightly different compression ratio for WIM files or because install.wim lacks integrity table (check option)
Yes option1 was used. Your wimlib compression explanation is probably the reason. EDUCATION x64 Install.wim after ESD conversion is lighter than EDUCATION x64 MSDN install.wim (3.35gb ESD converted vs 3.39gb MSDN). Different compression used.
Actually a solution was posted on TenForums over a week ago, and this is how it goes: Run regedit and locate the following entries: 1st Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0] 2nd Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0] Export both entries, then Delete the 2 Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 KEYS from the registry. Note: giving Administrators Full Control was needed to be able to delete them. Running "DISM /Online /Cleanup-Image /RestoreHealth ........" will be successful. To re-import the 2 registry entries, you may need to give "PackageIndex" and "Packages" full Administrator control, This is a workaround until Microsoft officially fix it.
hi can we safely create a dual boot of this windows creator edition with existing windows using 45 gb unallocated partition space?