TR Forums

"Bootmrg"? file and later a "Boot" folder containing "memtest.exe".

Ok, I use W7 (was W10 dual boot) and cleaned W10 off of it.
Then I disconnected W7 and installed W10-1809 onto it's own ssd.

The original W10 ssd was formated and my data file copied back onto it.
There were no protected files on this disk.

I don't "know" W10's habits maybe installing it created the protected boot file on
the other ssd.
But later fighting to erase the new file, the "boot" folder with memtest showed up
and I'm going...what the bleep?
What program goes around installing memtest on your computer?
I did not try to run the memtest.exe file by the way.
-----------EDIT------------------
Ok, memtest probably come from installing "unlocker" even tho
I did not see a check box for it. OOPS.
------------------------------------

Oh, the problem with all this was that my computer kept booting to the old dead
W10 ssd instead of my W7 ssd.
Bios boot setting just would not stay.
Bios saving stated "no changes to save" when I set the correct boot order.

Finally dawned on me that the old ssd was still "active" so I inactivated that and "unlocker"
after several tries finally let me delete the boot file and folder.

So far the pc is booting correctly to W7 now.
So any idea where the unwanted file came from?
Keep thinking "am I infected" Spybot system scan found nothing.

Thanks.

Sounds like you had an unclean install. I have basically given up on trying to dual boot anything since Vista/Win7 with their switch to BCD. Too much hassle and the fact that I can set up VMs easily to test things.

https://forums.guru3d.com/threads/c-boot-folder.366735/
https://www.sevenforums.com/general-dis ... drive.html

For future reference, you really should disconnect all other drives when you are attempting clean installs.

BTW, as a fellow forum reader, please do not manually break lines and let wrapping does its job. I am not on a phone screen and your text is reading weird.

Flying Fox wrote:

Sounds like you had an unclean install. I have basically given up on trying to dual boot anything since Vista/Win7 with their switch to BCD. Too much hassle and the fact that I can set up VMs easily to test things.

https://forums.guru3d.com/threads/c-boot-folder.366735/
https://www.sevenforums.com/general-dis ... drive.html

For future reference, you really should disconnect all other drives when you are attempting clean installs.

BTW, as a fellow forum reader, please do not manually break lines and let wrapping does its job. I am not on a phone screen and your text is reading weird.

"Disconnect all other drives"...
A pain, but I'll remember to do that from now on. Thanks.


The manual line breaking thing is from my Emails that are from phones.
When I reply with Thunderbird the quoted message line is just one single long line that disappears off into the distance.
I have to break them by hand just to see message.
Will try to remember to not do that here and see how it goes.

Thanks again.

Flying Fox wrote:

For future reference, you really should disconnect all other drives when you are attempting clean installs.

I second this.
PITA but its the only way to get a clean install when windows scans the drives for old installs of windows.

Aranarth wrote:

Flying Fox wrote:

For future reference, you really should disconnect all other drives when you are attempting clean installs.

I second this.
PITA but its the only way to get a clean install when windows scans the drives for old installs of windows.

Agreed. It's been my SOP forever (ie pre-XP)... and the odd time I forget, I inevitably regret it.

UberGerbil wrote:

Aranarth wrote:

Flying Fox wrote:

For future reference, you really should disconnect all other drives when you are attempting clean installs.

I second this.
PITA but its the only way to get a clean install when windows scans the drives for old installs of windows.

Agreed. It's been my SOP forever (ie pre-XP)... and the odd time I forget, I inevitably regret it.

I'll heartily endorse this as well. Given the potential for drive enumeration glitches, OS installer bugs, and pilot error, the chance for screwing things up is just too high if you leave any other drives connected.

UberGerbil wrote:

Aranarth wrote:

Flying Fox wrote:

For future reference, you really should disconnect all other drives when you are attempting clean installs.

I second this.
PITA but its the only way to get a clean install when windows scans the drives for old installs of windows.

Agreed. It's been my SOP forever (ie pre-XP)... and the odd time I forget, I inevitably regret it.

The last time I forgot to do this the Windows drive ended up being a different letter than C:.

It applies to both internal and external storage, BTW. Make sure you have no external HDDs or thumbdrives connected (other than the one you're installing from, if you're installing from a thumbdrive).