I'm hoping for an update about the above bug, which has been affecting TrueCrypt encryption users who have upgraded to NIS 2010. It also appears to be affecting PGP encryption users too. I have repeatedly raised the fault with Norton support, as have many other users, who have escalated it all the way to Symantec's 'Developer Level' as a bug within NIS 2010, but no information is forthcoming. The only fix appears to be to downgrade back to NIS 2009, which is where I have been for months now.
TrueCrypt (and I believe PGP) when decrypting data turn the result into a 'Windows drive' (known as 'mounting') which can be browsed like any other drive or removable media. When no longer required, the 'drive' is dismounted via the program, and it disappears from Windows. The fault occurs at this dismounting point - an instant Blue Screen Of Death and switch-off about 90% of the time I dismount.
I used to have a similar but slight problem when dismounting a TrueCrypt drive under NIS 2009 (see my post last year) but this only ever produced a minor error message, and so I never invested the time to pursue a solution. Under NIS 2010 however, a BSOD almost every time I use TrueCrypt is not something I can ignore.
Extensive details & crash logs etc have been already uploaded by Norton's support, but there exists no means for users to know if or when it is safe to return to NIS 2010. It's too big a process to do casually, and there appears no mechanism for Norton to inform customers if/when their developers deal with the issue. Windows crash logs all point at a Norton driver.
I'm hoping, without reraising yet another fault, that someone in Symantec's administration can shed some light on the state of this increasingly widely reported bug? A lot of TrueCypt users are anxious for a fix.