PC2: (Intel D945GCNL motherboard) Booting from IDE CD-ROM using PLOP 5.0.11, loads USB-HD menu, when starting Windows XP install also chokes at the start "unable to load \WINSETUP\XPPSP3\I386\BIOSINFO.INF". PC1: (AsRock P4VM800 motherboard) Booting from SATA CD-ROM using PLOP 5.0.11, loads USB-HD menu, when starting Windows XP install chokes at loading KBDES.DLL, before the partition text mode screen. PC2: SATA HD, IDE CD-ROM, boots from USB-HD and reaches Windows XP partition screen in text mode setup (WORKS OK) PC1: SATA HD, SATA CD-ROM, does not boot from USB-HD I use WinSetupFromUSB to create a standard installation, using Windows XP, Windows 7, and UBCD as sources. For testing, I created a primary partition of 64GB, and a second primary partiton with the rest of the drive. I will try to detail as much as possible. However, this problem is relatively straightforward to fix and easy to avoid in future – don’t use system optimizing utilities that may compress the Windows system partition and don’t try to compress it manually.Thanks for your feedback.
Unfortunately Windows does nothing to prevent an ‘optimizing’ program (or a user) from compressing Bootmgr – even though it means that Windows will not boot… This command decompresses (/u) all files (*.*) on the c:\ drive including hidden and system files (/a). Note: if your Windows system drive is not c: then change the c in the command to your drive letter e.g. The error message should not appear and Windows should start up normally.
Type Exit and press Enter to restart the computer.
In this case you would need to press ‘Load Drivers’ and browse to your RAID drivers so that your version of Windows can be listed. [Note: if using RAID for multiple hard drives you may not see your version of Windows listed in System Recovery Options, during the loading of the recovery process. If the repairs fail and/or the computer does not restart into Windows normally, proceed with the 5 step fix as follows:īoot into the System Recovery Options again but this time select ‘Command Prompt’ instead of Startup Repair – this will take you to a windows Command Prompt. If successful you can then restart the computer and Windows may boot up normally. Select ‘Startup Repair’ and wait until the repair attempt completes. Windows 10/8/7/Vista Fixīoot into the System Recovery Options using the preinstalled Advanced Boot Options or a Windows installation/recovery DVD – see the illustrated tutorial at Sevenforums for instructions if required.
The fixes for Windows 10 and all earlier versions of Windows are very similar – they require you to recreate the BOOTMGR file. You manually compressed the whole of the system partition (via the drive’s Properties window). This is what happened in my customer’s case.įile compression (even when done properly) may slow down system performance anyway so it is a lousy thing for a ‘speed booster’ utility to do… Such a program often causes this problem by compressing the whole of the system partition (usually the C: drive) to save space – including the crucial BOOTMGR file. You installed a ‘Speed Booster’ or ‘System Optimizer’ type of program – perhaps one with grand claims of boosting performance and with a super duper registry cleaner thrown in… See ‘ do I need a registry cleaner’ – the short answer is No.