I have two computers (different hardware) both running win 7 64bit with truecrypt on them, virtually identical installs. One computer keeps corrupting the TC boot loader 2-3 times a week, the other one has to my memory never done it, They get about the same amount of usage. Any ideas as to what could be the culprit.
I have worked through this with a number of folks over time. Not always the case, but you likely have some software program updating and that update keeps "walking on" the bootloader. In your post you mentioned that the two computers are almost identical. Maybe you will get lucky and realize which program you might have on the one that keeps jamming you up vs the one that runs great not having the software. Maybe? The TC bootloader occupies the same space a normal MBR. Some software updates like to change things in that area. Those are poorly designed but still some do. This is where I would recommend starting out your search.
Thanks Palancar, I will try to go over it the next few days, you're right, there some programs on the trouble machine that are not on the other. When you say update, do you mean update as in program tries to go on the internet?
Yes. I have seen times where pieces of software update and during that process they sometimes write inside the space used by the TC bootloader. Its really crappy software but they do it anyway. If you find the offending software is needed for work or whatever and can't have updates suspended you have an easy option. It is very easy to create a bootable USB to launch the machine. The USB only needs to be present for 1/2 a second to authenticate during pre-boot. That is why its called PBA in truecrypt lingo. Just insert it and enter your password and the second the password is accepted you can remove the flash. The side benefit is that no person can re-write the bootloader seeing as you remove the flash before the OS mounts. I have done this literally thousands of times and its a snap. ps - you need to make sure your computer will boot from USB but most do these days. A quick look in your bios will reveal the answer!!
