diskpart problem on x64 build .. not enough storage (solved)

Hi all

I have a problem that i encountered using latest build of Win81PESE ... we use diskpart scripts to deploy new software on our Acer laptops and everytime it's used on the x64 build you get the error "Not enough storage is available to process this command" all the time .. this is on certain laptops that only have 2GB of memory. if i use the x86 build it works without a hickup .. x64 build uses 1.2GB of avalible memory and the x86 build use 800MB. the builds are exactly the same, no drivers included or anything .. and it has worked on x64 before using older versions of Win81PESE builder .. i'm at a loss as to why this error has suddenly manifested itself, i don't think it's a memory problem since my old x64 build wim file was almost 900mb and now it's only 530MB without extra drivers ..

Anyone have any idea what could be the issue here? It's driving me nuts :)

Maybe using:
Finals\PostConfig --> Compression --> maximum

will gain you required memory on 2GB laptops !?

Which project version are you using? (latest?)
Which language?
I use test laptops with only 1gb of memory, and can confirm that memory "should" not be a problem. Specially if you don't use big aps with "run from RAM".
Not saying that it could not be memory related...
What does it say in Build\2- Shell % Config\FBWF cache size?
On the latest Win10PESE, diskpart doesn't seem to work at all for me (but diskmanagement does!), so it could be worth investigating.

i'm not sure which version i am using atm its likely the october build it says v57 in winbuilder not sure if that is the build? i use english ISO source but swedish language etc from my host pc.

Yes after further investigation it does seem that it is not a memory issue (FBWF is 768MB btw, i tried as low as 256 same result). But on x64 build disk manager freezes (its stuck on loading disk configuration information ..) , u never get to see any disks at all and if i use diskpart in cmd it just hangs on load, i can never imput anything like disk list etc .. so it seems to be related to the disks of some sort .. on the laptops that have issues the HDD is a eMMc drive that is builtin on the motherboard. since i don't have any drivers included on my own could it be drivers that is included by Win81PESE by itself? or maybe it is not driver related at all ..

EDIT: I also tried removing "fake disk" app from my build but with same result.

on the x86 build disk manager works just fine, it finds the emmc disk and my usb etc and diskpart works without any issues.

I'm afraid i do not know what version i had before that used to work since i deleted it but i believe it was a version dated back in march/april atleast.

EDIT: i will try the latest version from december to see if it works any better. will update.

ok out of the box the december release works on x64 build 

now i will add my custom apps and see if it breaks or continue to work .. if it breaks i have alot of work to do i guess 

BTW while i'm here if you have any solution to another issue i have with laptops that does not have full size keyboards (ie u need to press numlock or if u print some letters to the right on the keyboard instead will write numbers) is there a way to have numlock activated by default?

Thanks for doing all those tests!!! I'm on my break now, not a lot of time, but is diskpart also working for you now?
The diskpart issue you mention looks a lot like mine, so I'm interested in how that works out for you. As I said, I normally use the "gui" version (diskmanagement), but of course diskpart should also work, so again, I'm interested.

About numlock, yes, there's an option for it (Build/ 2- Shell & Config/ Numlock), but I'm not sure if you want it *on* or *off*? Well, give it a try, I hope it works as you expected.

Just a question: Why are you using Win8.1SE? I found it to be my least favorite project, I would even prefer Win10PESE over it, because it creates a smaller boot.wim, and should be even more compatible (hardware) than 8.1SE. Just wondering...
(Win8PESE is my favorite of all for now [small boot.wim], I'd even use Win7PESE, but that has some timing issues on bootup sometimes, which I hope to resolve someday...)

Yes diskpart now works even with all my apps and drivers reinserted into the build 

thanks for the numlock tip i will try it out!
EDIT: that worked 

I dunno, i use win8.1 since it was the highest version out there when i started with this project i have never tried the windows 7 version even, since it works for what i need it for i had no need to switch for anything else  . Tho i would ofc like to use Win10PESE but before it had 32bit support it was unusable to me since i have 32bit apps that has no 64bit version and is needed for the work we do here :( i tried the recent Win10 Build with 64bit support and it works fine but on some PCs it just seems to start up with black screen and mouse pointer and nothing more happens so i figured maybe it was not stable enough yet for me to switch to it .. i can't have it fail on any of the PCs i use it for, when it works fine on all PCs i will sure make the switch to 10 

Well, maybe the more systems you can test on, the more valuable input you can offer here to solve any problems. After all, we're all "enthousiasts" here (not a company) so we all can help to make the projects better.
Yes, Win10PESE 32bit support has improved a lot over the last weeks and months, so that's not a reason anymore not to use it 

But if you like 8.1SE, no reason not to stay there. 8.1SE testers are needed, too!

i will build a test usb stick with w10 and try it on some pcs and report back on the w10 section when i have problems 

mrchisholm,
Very nice to see your problems (diskpart, capslock) are fixed for now and nice of you to do some more testing on Win10PESE!!
I hope you will stick around on this forum!

I'm not really sure what the exact cause was of your diskpart problem, but it could be related to mui files and international settings. ChrisR just did a fix on the code last week, that took care of a lot of my problems as well (diskmanagement, cmd.exe), so it could be related.
DISKPART works for me too, now so that's more good news!
Wouldn't it be great if ALL our problems could be fixed in just one day (like this thread)
 

One more thing: maybe you want to change the topic title and add "Solved" at the end? (edit message one, then edit title).

Also, are there any "special tricks" you use in your diskpart scripts? Maybe you want to share some of them here? Thanks!

done 

It's not really my script, we use app from Acer that partition the hdd on laptop/tablet and transfer wim files for installation (after reboot) so i have not studied them much  . but i'm about to atempt to use diskpart in conjunction with imagex to copy the partitions to other pcs where we have replaced the motherboard (hdd is on mbd, emmc etc .. ) since normal image tools like clonezilla and acronis will not sucessfully restore the images (it will never boot windows for some reason but go to repair mode everytime it boots).

normal image tools like clonezilla and acronis will not sucessfully restore the images

"image tools", hmmm, interesting...
http://theoven.org/index.php?topic=1141.0

Have you tried Terabyte Image for Windows? It has never failed me (even in cases where Acronis did fail).

thank you i will try it when i get time but i'm not hopefull that it would succeed 

I use to use diskpart and dism commands to partition drives and apply images all via a WinPE command prompt...

Until I found WinPESE and now I can SEE what I am looking at and doing...

Yes, we are blessed with WinPESE! 

Of course, diskpart has more "power" if you want a scripted solution, but actually using a GUI for partitioning and disk management is actually a good idea, I think (like you said, sometimes it's good to SEE what you're doing).
Disk management is the only thing left here that needs manual input, all the rest of setup and postinstall is automatic/ unattended, etc.

I have to know KYHI, do you use WinNTSetup to apply your wims as well? (I LOVE it!!!, another masterpiece by JFX).

(Not off-topic, because the original issue is solved anyway...)

no, dism apply-image