[SOLVED] [Win10 x86] Upgrade fails. Cannot create ramdisk

[WacoJohn]

Google search indicates this is a widespread issue, ... and the fix is highly published .... but it is not fixing it for me.
W10 Update assistant says I need to update W10 ... from 10240 to 15063. So, I go for it and it goes well up to the mandatory restart .... and get an error that there is not enough memory to create a RAMDISK and I end up still with 10240.

Below is the solution I found but you will see that it fails ... for me. I am stumped.

C:\WINDOWS\system32>bcdedit /enum all

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {755b2629-26b6-11e5-ba62-9df8483dc853}
                        {755b2626-26b6-11e5-ba62-9df8483dc853}
                        {755b262a-26b6-11e5-ba62-9df8483dc853}
                        {755b2627-26b6-11e5-ba62-9df8483dc853}
                        {755b2628-26b6-11e5-ba62-9df8483dc853}
                        {e2856818-9f48-11e7-a31f-806e6f6e6963}
                        {e2856819-9f48-11e7-a31f-806e6f6e6963}
                        {e285681a-9f48-11e7-a31f-806e6f6e6963}
timeout                 2


Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {755b2632-26b6-11e5-ba62-9df8483dc853}
displayorder            {current}
bootsequence            {755b2631-26b6-11e5-ba62-9df8483dc853}
toolsdisplayorder       {memdiag}
timeout                 0


Firmware Application (101fffff)
-------------------------------
identifier              {755b2626-26b6-11e5-ba62-9df8483dc853}
description             EFI USB Device


Firmware Application (101fffff)
-------------------------------
identifier              {755b2627-26b6-11e5-ba62-9df8483dc853}
description             EFI DVD/CDROM


Firmware Application (101fffff)
-------------------------------
identifier              {755b2628-26b6-11e5-ba62-9df8483dc853}
description             EFI Network


Firmware Application (101fffff)
-------------------------------
identifier              {755b2629-26b6-11e5-ba62-9df8483dc853}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager


Firmware Application (101fffff)
-------------------------------
identifier              {755b262a-26b6-11e5-ba62-9df8483dc853}
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Internal EFI Shell


Firmware Application (101fffff)
-------------------------------
identifier              {755b262b-26b6-11e5-ba62-9df8483dc853}
description             EFI USB Device (KingstonDataTraveler 3.0)


Firmware Application (101fffff)
-------------------------------
identifier              {e2856818-9f48-11e7-a31f-806e6f6e6963}
description             EFI USB Device


Firmware Application (101fffff)
-------------------------------
identifier              {e2856819-9f48-11e7-a31f-806e6f6e6963}
description             EFI DVD/CDROM


Firmware Application (101fffff)
-------------------------------
identifier              {e285681a-9f48-11e7-a31f-806e6f6e6963}
description             EFI Network


Windows Boot Loader
-------------------
identifier              {755b262c-26b6-11e5-ba62-9df8483dc853}
device                  ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Win
re.wim,{755b262d-26b6-11e5-ba62-9df8483dc853}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-us
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Win
re.wim,{755b262d-26b6-11e5-ba62-9df8483dc853}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes


Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {755b262c-26b6-11e5-ba62-9df8483dc853}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {755b2632-26b6-11e5-ba62-9df8483dc853}
nx                      OptIn
bootmenupolicy          Standard


Resume from Hibernate
---------------------
identifier              {755b2632-26b6-11e5-ba62-9df8483dc853}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {755b262c-26b6-11e5-ba62-9df8483dc853}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
pae                     Yes
debugoptionenabled      No


Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes


EMS Settings
------------
identifier              {emssettings}
bootems                 No


Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200


RAM Defects
-----------
identifier              {badmemory}


Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}


Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}


Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200


Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}


Device options
--------------
identifier              {755b262d-26b6-11e5-ba62-9df8483dc853}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume4
ramdisksdipath          \Recovery\WindowsRE\boot.sdi


C:\WINDOWS\system32>bcdedit /deletevalue {badmemory} badmemorylist
[COLOR=#ff0000]An error occurred[/COLOR] while attempting to delete the specified data element.
Element not found.


C:\WINDOWS\system32>

This was 'supposed' to fix my problem ... but it fails (in red).

 

[Sysnative Windows Update]

Re: W10-32 upgrade fails. cannot create ramdisk

Hi there,
please try upgrading your system from a Clean Boot state using Media Creation Tool.

https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

 

[WacoJohn]

Re: W10-32 upgrade fails. cannot create ramdisk

Thank you. This MAY be beyond the scope of your help .. because this is a low-end 'tablet-pc' running W10-32 HOME. It has 1 micro USB port and only 1GB of RAM and a 32GB SD card. It has a docking station .. for use as a 'PC' or can be used in TABLET mode when 'hand held'. I use it mostly as a PC/laptop ... and that is where I am trying to update W10.

The current installed build is 10240. It wants to update to current build .... and I get the 'not enough memory .... ramdisk' problem.

I did the clean boot but it did not help. I THINK I need to do a media creator exercise ... but not sure how to do that with this hardware. I don't see Media Creation Tool as anything installed. I don't know of a thumb drive with a micro connector so if I am to 'burn' something with Media Creator, that will be an issue. Is this something I download? Sorry ... not as sharp on this device as I am on real laptops.

I have contacted the mfg support but have little confidence in their help ... remains to be seen if they reply. The product is an Emetic EWT935DK.

 

[xilolee]

You could try this command:

bcdedit /set {bootmgr} badmemoryaccess no

I tried it and it adds this value in the bootmgr, but I'm not sure it will work on your device, for your problem.

 

[WacoJohn]

I tried it but it did not help. As I mentioned, .. the 'ramdisk' problem is well known to the Internet. There must be some kind of solution.

Edit: I decided to try the WU Troubleshooter. It SAID it fixed something. Trying again from there. Takes a good while. Downloads the update every attempt and it is big.

 

[WacoJohn]

You were right in the FIRST place.

please try upgrading your system from a Clean Boot state using Media Creation Tool.

I was using the Windows 10 Upgrade Assistant which resulted in the ramdisk error. MCT updated good and proper. I stayed back from it because I did not CLEARLY understand how it worked.

Again, .. thank you, Sir.

 

[Sysnative Windows Update]

I'm really glad the solution worked for you.

Best,
Mihael