Can I move NTDETECT, NTLDR and BOOT config file without breaking anything?

[MichaelD]

I loaded Windows onto a HD that was already partitioned.

Windows put all the main files (Program Files, Windows, Pagefile etc) onto the C drive, but it put NTDETECT/NTLDR and the boot config file to one of the other partitions. 😕

Why the heck does it do that? There's PLENTY of available space on the C drive.

Can I move those files from D to C where they belong? Will it break my install?

Thanks.

 

[nweaver]

yes, it will break it...


are you sure those ones aren't from an older install on that second drive?

 

[MichaelD]

Yeah, I'm sure. I.E. those files that are on the other partition do not exist on the "C"/Windows partition.

This just sucks. Windows is old at this time; there's got to be a way to move those files over to where they belong.

It's a bit late, but now I'm remembering; "disconnect all other HDs before installing Windows!" 🙁

It just sucks that the most prevalent OS in the world can't get its' install utility straight! I mean, "install to "drive" SHOULD mean just that; install the OS to the specified drive. Don't put this/that/the other thing anywhere else!

 

[imported_Com80787]

Before you go and bash Microsoft why don't you look up the term bootsector?

All PC operating systems will put boot data (NTLDR, in this case) in the bootsector. The bootsector is the FIRST section of a hard drive - and if the drive is partitioned it will be the first partition. If there are multiple drives it will be the first drive, first partition.

The BIOS executes the data in the bootsector. If the data is not present no OS will boot during a regular startup. Therefore if you remove NTLDR or any other boot data from the bootsector your system will not boot. This has been the case for the past 20 years. The BIOS expects this data in the pre-defined bootsector. What do you expect the BIOS to do logically? Search 500 gigs of data at every boot and guess at what data should be in the bootsector?

That is your answer as to why Microsoft does "this crap". If it really bothers you THAT much you have two options

1. Contact system board manufacturers and convince them to develop a means to boot operating systems in a manner different than what has been used for the past 20+ years

or

2. Make the first drive, first partition your OS install partition (which is how it should be in an ideal setup to begin with BTW), and the other partition your non-OS partition.