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?
Well, why didn't you post it here and made me all this work?!? BTW, wouldn't removing 2 registry entries without removing the packages leave something broken??? EDIT: I just checked TenForums and actually removing the 2 registry entries alone can make the errors re-appear. Someone posted that to make errors go away completely you need to move: C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum to another location, but that is not the correct way to get rid of a system package either, so I think WIM_Tweak or CBSEnum is the only truly healthy way to repair DISM. System packages have to be de-doupled and uninstalled, not removed/moved, if you do not want to risk breaking the OS.
At the time I searched MDL but found no reference to this issue, then MDL went for 3 days and the whole thing was forgotten, I did not think many people were facing the same issue!!. I bought a new notebook and wanted to migrate my old installation (which was working fine) into it when I noticed that it freezes for more than an hour at 11% when I perform CHKDSK /f /r.. So I thought to perform the DISM stuff .. I was busy thinking it is the new Notebook, but I noticed some people reported sorting their problems by converting the install to WIM or ESD or vice versa, and some by dragging the install.wim to a location on the C:\ drive, other by finding the installation number like #1 is Pro and #2 is Home etc.. and many other suggestions that I tried but did not work. Then I came across the registry solution that worked, at that stage, I was busy finding out what else is wrong.. Any way, I ended performing a fresh Windows and applications installation which I always prefer. But every couple of days, I find that I have forgotten this application/utility or that configuration. Just for reference, the 11% freeze finishes with no errors after an hour and a half (for some people it took over night). I hope Microsoft releases an update that includes fixes to these and other issues soon (the latest to date is 251).
I'm facing a problem on 1703 in one of my installations that I can't find a way to solve. When using search, some windows desktops apps are listed but they don't open when I click them. As an example, when searching for notepad, Notepad (Desktop App) will be listed at the top, but nothing happens when I click it (going to start>Windows Accessories\Notepad opens fine). I've done a sfc /scannow and reinstalled w10 while maintaining everything but the problem remains.
Please sk_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10196116.iso.SHA1: 13A938BAD0AAD847DE08BBECF519F0A1DD01CFDE
Click on the icon to mark it then hit Enter key to start the application, in case the problem is with the touch pad.. Also, try refreshing you icons.
Please, I need : fr_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10204211.iso SHA1 :9B0C595397480A4830CD6669C5817B99B967C5A8 fr_windows_10_enterprise_version_1703_updated_march_2017_x86_dvd_10191846.iso SHA1 :ACEF86D3159646F6059B99376C9A580B1640F7F3