Same. What the f**k have they done? EDIT: Remake the boot partition... It just died here. Use CMD and Installation Media: diskpart list disk select disk # Note: Select the disk where you want to fix the EFI System partition. list partition select partition # Note: Select the System partition. Should be 100MB, FAT32. format quick fs=fat32 assign letter=s list partition list volume Note: Note the volume letter where the Windows OS is installed. exit bcdboot X:\windows /s S: Note: Replace "X" with the volume letter of the Windows OS partition.
When do we expect this to go "RTM"/"GA"? I have to do a re-install as there is something really wonky with my Windows 10 1709 installation, but I tend to always do a fresh install with every new Windows 10 release so I'm debating whether I should just stick with the issues until the new ones is out or just do a re-install now..
I have the same thing. And what worse is that the USB I created for clean install lands me in the Advanced Menu straight after I choose the keyboard layout, so I can't format or install anything now!
Can anybody help with this file? Spoiler: UUP to ISO converting issu CAB->ESD: Microsoft-OneCore-ApplicationModel-Sync-Desktop-FOD-Package-amd64 CAB->ESD: Microsoft-Windows-Hello-Face-Resource-A-Package-amd64 CAB->ESD: Microsoft-Windows-Hello-Face-Resource-B-Package-amd64 CAB->ESD: Microsoft-Windows-Hello-Face-Resource-C-Package-amd64 CAB->ESD: Microsoft-Windows-InternetExplorer-Optional-Package-amd64 CAB->ESD: Microsoft-Windows-LanguageFeatures-Basic-en-us-Package-amd64 CAB->ESD: Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package-amd64 CAB->ESD: Microsoft-Windows-LanguageFeatures-OCR-en-us-Package-amd64 CAB->ESD: Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-amd64 CAB->ESD: Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package-amd64 CAB->ESD: Microsoft-Windows-MediaPlayer-Package-amd64 CAB->ESD: Microsoft-Windows-QuickAssist-Package-amd64 CAB->ESD: OpenSSH-Client-Package-amd64 ============================================================ Creating install.esd . . . ============================================================ [ERROR] "\Windows\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17093.1000_none_fe953b4fdd6b6a56\Flash.ocx": blob not found SHA-1 message digest of missing blob: 4936450c84b8777478400245ca1d45b5034f3330 ERROR: If this is a delta WIM, use the --ref argument to specify the WIM(s) on which it is based. ERROR: Exiting with error code 55: A file resource needed to complete the operation was missing from the WIM. Errors were reported during export. Press any key to exit.
Version 1.9.1 . Do I still need to update it? P.S: I am still getting the same error after updating to version 1.10
I had the same problem in previous Build with both upgrade and clean install thinking my SSD had gone bad only to find out it had not. The only way I could do the installation was reverted to legacy at the BIOS and used the mounted ISO to do the upgrade. It's frustrating though.
From what I'm reading here and my own personal experience, I'm going to stick with 17083 and give this version a miss. The latest UUP and abbodi1406's uup converter 14 made me an error free 17093 ISO, but I've had no luck getting it to install. Even tried to use the ISO to update an existing Windows 10 OS on real hardware. Post install reboot was to a blue-screen. At least the install process was gracious enough to automatically roll itself back to the original OS. That's the end of the line for my time investment in this half-baked version.
Confirmed. Clean install and still not able to shutdown and boot normally. Use the USB and click [Repair My Computer] and then just select [Exit and continue to Windows 10] get me back inside. Note: The PC will reboot when you choose this option, just let it reboot and it will get to the installed Windows 10
Hi! I have the same problem on this build - 17093. After update all works fine but when shut down PC and next morning turn on, it reboots constantly. I thought it was SSD problem but I checked it twice and now know it's the boot issue with this build. We should report it to Microsoft because it's a critical bug.
Use the USB and click [Repair My Computer] and then just select [Exit and continue to Windows 10] get me back inside. only work