In any case the PWboot project is/was intended for BIOS and thus for MBR style partitioning. It is not needed (sizewise) and it will be unbootable on BIOS machines (because of the GPT) and unbootable on most UEFI machines (because of the NTFS filesystem which is not supported in the UEFI standard). You don't really need (or actually want) a GPT partitioned USB stick with a NTFS. Then there is the added complication of GPT. It is entirely possible that your USB 3.0 device might be ok if connected to a USB 2.0 port. The good news are that USB 3.0 devices are backwards compatible, i.e.
Maybe, integrating the right (which?) USB 3.0 drivers it is possible to install it, but then it is unlikely to work (as the project idea is) 'universally', it will likely work only on motherboards with a chipset for which the drivers are present. Windows 7 has no 'native' support for USB 3.0 motherboard controllers, so that is usually a no-no. Anyone have permissions issues that were resolved by somehow emulating a fixed disk, whether by flipping the removable bit, or using drivers, etc? You seemingly managed to put together more than one possible complication. I agree that the most likely reason I have permissions issues is because windows sees the thumb drive as a removable disk instead of a fixed one, but i still have to figure that out. The system has plenty of ram and no expectation to run heavy software. I'll give diskmod a try, although I'd rather just not use a pagefile.
I still can't update one the portable windows is running, but i should be fine for a while. For now, I've decided to slipstream all windows updates into the install.wim file that gets plugged into PWboot when building the flash stick. I presume that the Windows Update issue to be connected to the exact way the USB device is 'seen' by windows (Removable vs.įixed, but also 'Internal'/'external') maybe (just maybe) Diskmod may be of use (though cited on first page of the present thread you didn't specify if you are already using it ): Wonko.
Compare with: (no 'ready made' solution that I can remember for the PWboot, but it is possible that service groups in a 'standard install' are not 'as they should be, as well it could be an incompatibility with actual hardware).
'Installing' the drivers in Windows is not normally 'enough' to have them working when booting. of 11 - PWBoot 3.0.2>- posted in Project forge: Introduction What is PWBoot project? PWBoot stands for Portable Windows Boot project, this project aims to be make your Windows operating system to boot from USB storage media easily.Ībout USB3: You should disable 'automatic reboot on error' (or whatever the setting is) in order to be able to read the actual BSOD STOP ERROR. PWBoot stands for Portable Windows Boot project, this project aims to be make your Windows operating system to boot from USB storage media easily.