RM Build Disk has ruined another computer, help

[talksr]

What an annoying scenario.

This is not the first time this has happened either.

 

RM asked me to create a USB build disk to use on some of their RM one systems which refuse to network boot to our server.

I created said USB disk using their instructions and tested it on a test computer, it would not work.

 

I reported back to RM and put the USB drive back in the computer I work on ready to continue with whatever instructions they sent.

In between yesterday evening and today, the computer has rebooted for Windows updates and when it did, it successfully ran the USB drive which put it into RM Build Mode. Obviously, the build didn't start, and when I came in this morning, the computer had picked up an IP address from our RM server and was waiting for authentication details so I could select an image and build the computer.

I closed this and switched it off - nothing has been built and I did not log in.

 

Now when I boot my computer, it says:

GPT-formatted disk.

Legacy boot not supported. Press any key to reboot.

 

What can I do? I am unable to get it to boot back to Windows. Wouldn't mind but this is the system I use and has all sorts of software on it I would struggle to find again.

[synaesthesia]

Probably not the right forum for this, nor is it really a problem with build disks; it was left in your computer and did exactly what it needed to do!

I would suggest trying a repair from vanillia windows media or a reinstallation/upgrade where it keeps your files. If that's also CC4 then smartclient it back on afterwards.

[talksr]

Probably not the right forum for this, nor is it really a problem with build disks; it was left in your computer and did exactly what it needed to do!

I would suggest trying a repair from vanillia windows media or a reinstallation/upgrade where it keeps your files. If that's also CC4 then smartclient it back on afterwards.

 

The build disk was not working on my test machine, that is why I re-inserted it into my computer ready to sort it out, but time got the better of me. The system I use very rarely reboots in the evenings.

 

You suggested repair from vanilla Windows. Do you mean literally putting in my Windows 10 USB install drive and running through the repair options on there, if it gives me any? It is not CC4, it is just a stand alone system that I use.

[synaesthesia]

Then yeah, just boot from the Win 10 media and go through the troubleshooting options.

Firstly try the command prompt and make sure your files are there and it hasn't repartitioned/formatted anything. If it hasn't, then repair will work. Whilst you're in command prompt the first commands to try will be:

 

bootrec /RebuildBcd

bootrec /fixMbr

bootrec /fixboot

 

Give it a reboot and see if that works. Failing that, try a repair installation.

If it has repartitioned, time to dig out some recovery software I'm afraid.

[talksr]

Then yeah, just boot from the Win 10 media and go through the troubleshooting options.

Firstly try the command prompt and make sure your files are there and it hasn't repartitioned/formatted anything. If it hasn't, then repair will work. Whilst you're in command prompt the first commands to try will be:

 

bootrec /RebuildBcd

bootrec /fixMbr

bootrec /fixboot

 

Give it a reboot and see if that works. Failing that, try a repair installation.

If it has repartitioned, time to dig out some recovery software I'm afraid.

 

Thanks, already went on to it before you replied. Just doing a chkdsk /f C: and then I will try the three you recommend.

[talksr]

Thanks, already went on to it before you replied. Just doing a chkdsk /f C: and then I will try the three you recommend.

 

All of the commands worked other than /RebuildBcd which came back saying:

 

Scanning all disks for Windows installations.

Please wait, this may take a while...

 

Successfully scanned Windows installations.

[1] C:\Windows

Add installation to boot list? Yes(Y)/No(N)/All(A):

 

I selected Yes and it said, The requested system device cannot be found.

Re-tried and went for All. Same error again.

[synaesthesia]

Go for the windows repair tool, shouldn't take long.

[talksr]

Go for the windows repair tool, shouldn't take long.

 

Thanks, gave it a go but I get:

 

Startup repair couldn't repair your PC.

Press advanced options to try other options to repair your pc.

 

I tried Reset this Pc but it says:

The drive where Windows is installed is locked. Unlock the drive and try again.

[Andrew830]

When you boot the PC do you see the RMR top left in the screen before Windows loads, if so, hold down the two shift keys until the build process starts

[talksr]

When you boot the PC do you see the RMR top left in the screen before Windows loads, if so, hold down the two shift keys until the build process starts

 

Unfortunately not. This is not an RM system, it is my own vanilla workstation. I never installed an RM build onto it, the USB rm build disk just ran to the authentication stage, but never installed anything.

[ReadTheNetwork]

Sounds like your computer is booting legacy rather than UEFI. If your machine supports UEFI and you have an UEFI build disk then enable UEFI boot in your BIOS.

 

Otherwise, run a Windows repair and bring up a command prompt then do the following (ignore anything in brackets - this is just info:)):

 

Diskpart

lis dis (list the disks)

Sel dis 0 (0 being the number of the local HDD for the machine, containing windows)

Cle (clean the disk)

Con mbr (convert to MBR - legacy mode)

Cre par pri (create a primary partition)

For quick fs=ntfs (format the partition using NTFS)

exit

 

Then reboot. This should put your disk back ready for legacy.

Edited July 18, 2016 by ReadTheNetwork
Previously wrote a brief description on phone. Lengthened on computer

[Dos_Box]

Moving to Network Management forum.

[talksr]

Sounds like your computer is booting legacy rather than UEFI. If your machine supports UEFI and you have an UEFI build disk then enable UEFI boot in your BIOS.

 

Otherwise, run a Windows repair and bring up a command prompt then do the following (ignore anything in brackets - this is just info:)):

 

Diskpart

lis dis (list the disks)

Sel dis 0 (0 being the number of the local HDD for the machine, containing windows)

Cle (clean the disk)

Con mbr (convert to MBR - legacy mode)

Cre par pri (create a primary partition)

For quick fs=ntfs (format the partition using NTFS)

exit

 

Then reboot. This should put your disk back ready for legacy.

 

Thank you, will give this a go tomorrow.

[talksr]

Thank you, will give this a go tomorrow.

 

I had high hopes for this, all of the commands went through with no issue, but no same problem, when it boots, it says:

 

Non-System disk or disk error

replace and strike any key when ready.

[ReadTheNetwork]

Just to confirm what you've done so far.

You've wiped the HDD and converted it to MBR, so now if you try rebuilding it hopefully your build works on a MBR format rather than GPT. Let me know how far it gets, hopefully it might just run through.

Edited July 20, 2016 by ReadTheNetwork