How to increase the size of a bot.wim file up to 3 GB

Hi guys
How to increase the size of a bot.wim file up to 3 GB
the problem is more than 2.15 GB, you receive an error message

There isn't enough memory to create a ramdisk device.

Error code: 0xc0000017

win10pe_64bit

Best Regards

There isn't enough memory to create a ramdisk device.

1) check your total physical memory.

2) decrease Build\"2 - Shell & Config" Plugin --> FBWF cache size:

2 - Shell & Config" Plugin --> FBWF cache size: 2024

Is there a file FBWF cache size: 4096

Is there a file FBWF cache size: 4096

I do not have.

Search the internet about fbwf limitations and adjusting fbwf settings.
 You should experiment with related things.....

I need a file 2 - Shell & Config that gives RAM 4 GB

Best Regards

I have this same issue, however I con provide some more interesting information.

The build I have is built from a freshly downloaded Windows 10 1809 x86/x64 ISO created by the Media Creation Tool from Microsoft. The resulting image created from 'Just pressing' the -PLAY- button works fine on a machine with these specs:
Core i5-3340 on Gigabyte GA-B75M-D3V Motherboard
8GB DDR3 RAM
16GB Boot SSD
The image is hooked by and booted by 'Easy2Boot'
--This works A-OK

The second machine I have which does **not** work
Intel Pentium Gold on Gigabyte B360-AORUS-GAMING-3-WIFI
12GB DDR4 RAM
480GB Boot SSD
The image is hooked by and booted by 'Easy2Boot'
--This PC spits out a **There isn't enough memory available to create a ramdisk device (error code 0xc0000017)**

I have tried with all sizes for the FBWF and with IMDisk enabled and disabled, I've downloaded a new, clean Windows image, updated the project version, re-extracted the project zip and all while having AV totally disabled. I have also tried using the 'Basic' build with no apps. I'm about to tear my hair out on this one as I've had the build working once before on the motherboard above so I know it CAN work but there must be a setting I'm overlooking. Could it be something to do with the Bootloader? The shell or Something else? Any help would be greatly appreciated and I'm happy to answer any questions regarding my configuration!

Hi TM.Richard

I wonder how you miss using none Media Creation source.

See Reply 10
http://theoven.org/index.php?topic=2785.msg32701#msg32701
which seem to recently fix troubles of Coryc209 (Reply 12)



Edit:
*
Please ignore any pm spam advertisement after your post around now.

Some forum members have a childish habit to spam advertise other projects after each post around,
 Let us know if you get such a pm.

See You around.

Got it thanks Lancelot, looked at the link, backtracked to the Extended support page, read every.single.post this time, spotted the part about '*.esd' sources not supported, checked my extracted source, *.esd. --Sighed--

Will convert source and try again, that will probably fix the issue. Hopefully. Odd that the build works in virtual tests and old hardware but just not on 'new' hardware.

Got it thanks Lancelot, looked at the link

link and following  Coryc209 Reply 12 -->  Coryc209 download official iso

Will convert source and try again

Follow Coryc209 , not convert

Thanks Lancelot, not long after posting I was testing the converted files in a build which was successful and am now proceeding with customisation. Unless there is a specific reason why the Microsoft MCT's ISO is not compatible with the project other than it being an *.ESD source I intend to continue to use the converted files. Additionally the link in that post chain may give an "official" image, however, it is not from an official Microsoft Domain and I am not personally familiar with the site. As this is the case I would prefer to use the official Microsoft supplied source unless, as mentioned before, there is a good reason not to.

I appreciate the help thanks Lancelot!

Just updating here for others:
The ISOs downloaded from Microsoft's "Media Creation Tool" use *.ESD not *.WIM files. There is a link in the "Win10PE SE Release - Extended Support" page by Moderator Bob.omb http://theoven.org/index.php?topic=2594.msg31941#msg31941 which has a link to a tool that will allow you to convert the *.ESD file into a *.WIM file (Tool here: newbielink:https://www.chuyu.me/en/index.html [nonactive]) If you convert the necessary files the build should work as expected (at least it has worked fine for me in multiple test versions I've made) If you continue to have issues after converting please try picking up what Lancelot was putting down as it may still be image related.

Hi TM.Richard,

thanks for feedback 
I just put your feedback to Bob.Omb related topic post :
http://theoven.org/index.php?topic=2594.msg28247#msg28247

*
Specific reasons:
1)
Lots of People time to time fail to create projects with the sources they download from ms, we need a static reference to compare results.

2)
ESD when encrypted cause troubles .... , as a solution you can convert to wim (Thanks following links  ) but this alone does not solve Reason no 1.
 If you are experienced enough, conversion will work for you... But Dealing with Public users is a different kind of thing...
  For today It is easier for us to compare with the same source, Maybe this may change in future If we can not have solution 1.


See You around.