Skip to main content

Attempt to modify MBR of your disk: which disk is "your disk"

Thread needs solution

Please advise how to determine which disk your software is protecting or complaining about.  ie:  how to find out if it is C, D, E, or whatever. 

 

I was attempting to create a bootable ubuntu flash drive in "E" on my win10x64 system.  If you are protecting E then that is a problem as I need the flash drive to boot so as to install ubuntu.  On the other hand, if the program I downloaded to create the ubuntu boot flash is maliciously putting something in my "C" drive, then yes, I need to know what the H E L L they are doing to the MBR on my windows drive and get their site and tools blacklisted.

 

Why would a software engineer or programmer even use the phrase "your disk".  IMHO that is what a sales agent would say. 

 

Thanks for looking.

0 Users found this helpful

Joseph, if you were creating a bootable flash drive then this is what AAP would be 'protecting' against MBR changes and you would need to either whitelist the Ubuntu media creator program you are using, or else turn of AAP via the system tray icon while using that program.

I have seen the same issue myself doing similar tasks creating boot media.

Was this a True Image message?  If yes it is from the Active Protection feature of the application.  It is designed to stop modification of the MBR.

If this is an Active Protection warning I would question the software you are using as there should not be a need to modify the MBR on your system OS disk and that is what is monitored by Active Protection.

If you are already using or running a dual or multi-boot system then there would be more than 1 MBR however, since your target is a flash drive I find what you have posted highly suspicious.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Joseph,

Thank you for bringing this up to our attention! I've passed this forum thread to the product team.