Win10XPE - Build Your Own Rescue Media [2]

I think I understand a bit better now.

To test a bit I ran several passes (5) of CrystalDiskMark where the size limit was set to default (1gb) (this is all in VM with 4gb allotted). This resulted in the RAM drive ( B:\ ) being utilized ~80%, which sounds about right considering it is set to 1.28gb. It did not affect the free space readout of the boot drive ( X:\ ). It also did not affect the memory used in Task Manager -> Performance tab in the PE.

I further created an additional PE with the 2048mb/2gb cache size, and was able to see that the PE Performance tab then shows 2.66gb memory in use, and drive X:\ (boot) shows to be 2gb in size (instead of 1gb). So that makes sense.

Yessssss. Greater the memory space. Stronger it becomes

Kyhi said:

Dang, you both had me wondering.... - The cache size is the available free space AFTER the Boot.wim is load into memory...

And you can decrease the size of your Boot.wim by adding your Portable Program to > "\Win10XPE\Custom\x64\IsoRoot"
Or by Not Setting All Programs to RAM

Thanks :) Yes, I do add some to IsoRoot also. I probably am putting too much into the boot.wim. I should probably do more of a hybrid approach. I'd probably want to keep at least backup/recovery/partition apps inside the boot.wim, just in case of installing on a 1-port USB system like a Surface. Not something I'd personally run into probably, but someone reminded me of that scenario where you might want to disconnect your PE usb drive for an external HDD to load a backup image from, so that at least you'd have those programs already loaded in memory as it couldn't load them off the USB drive of the PE. Maybe a bit of a far-fetched scenario but it could happen :)

Ok so I've finally successfully created a USB of this (I think)

My original problem for creating this was because I received a BSOD related to a missing winload.exe file and giving me the error 0xc000000f

I've tried a system restore from a different store points a couple of times, but it doesn't seem to fix anything.

So someone had suggested I make this drive in order to "boot it to zip the dump files" and then upload them.

My question is, how do I make this boot so that it will zip the dump files?

I'm not sure exactly what to do as I've never zipped dumped files, so it's all new to me.

Thanks!

AuraticTrance said:

Hello everyone, thought of posting this on oven but seeing the discussion here i'm keeping it here, i'm using Bob.Omb's WinPE. I've placed my WinPE on my multiboot USB. The autorun.cmd present in the root of PE's folder doesn't start it seems to be because of a changed path. The path to my WinPE is DriveLetter:\RECOVERY\PE. I've looked inside pecmd but there's nothing related to autorun.cmd in it.

Since I don't have Bob's XPE I cannot say if he moved the autorun.cmd to the root but I's supposed to be in System32.

you can verify this key

Code:

[HKEY_LOCAL_MACHINE\.Default\Software\Microsoft\Windows\CurrentVersion\RunOnce\Autorun"="hiderun.exe /w Autorun.cmd"

You can also check if the root is added as part of the system Path

Code:

HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\path

Besides this, there could be multiple different other reasons for your command not to run.

AuraticTrance said:

I don't see any Run or RunOnce keys on mounting loading the hives, and PATH doesn't have the root folder

to my surprise there are two autoruns.cmd - one in Sys32 and one in root

Try to search the whole registry for "autorun.cmd"