I have used TrueCrypt (www.truecrypt.org) to encrypt my user profile and
data. Windows Defender chugs along fine until it tries to read HKCU, then it
gets the 0x8050800c error. If I use a non-encrypted profile to run WD, it
works fine. I am certain my profile is not corrupted as some have suggested
this could cause the error. I've tried this on two machines, one with a
cleanly created and encrypted profile and I get the same message.

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1361.6

System Information report written at: 04/05/06 06:55:31
System Name: VALKYRIE
[System Summary]

Item Value
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Name VALKYRIE
System Manufacturer Motion Computing
System Model LE1600
System Type X86-based PC
Processor x86 Family 6 Model 13 Stepping 8 GenuineIntel ~1500 Mhz
BIOS Version/Date Motion Computing - LE1600 A06, 1/18/2006
SMBIOS Version 2.34
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180
(xpsp_sp2_rtm.040803-2158)"
User Name VALKYRIE\Aaron
Time Zone Eastern Standard Time
Total Physical Memory 1,536.00 MB
Available Physical Memory 911.30 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 2.29 GB
Page File C:\pagefile.sys

Hello Aaron,

error: 0x8050800c.
If this is on a basic disk partition, you may be able to get beyond this by
completing a CHKDSK run on the partition. If it is a dynamic disk, this is
a bug. We expect a fix to be available soon, via the normal update process
within the program.
--

"Aaron Oneal" wrote:

> I have used TrueCrypt (www.truecrypt.org) to encrypt my user profile and
> data. Windows Defender chugs along fine until it tries to read HKCU, then it
> gets the 0x8050800c error. If I use a non-encrypted profile to run WD, it
> works fine. I am certain my profile is not corrupted as some have suggested
> this could cause the error. I've tried this on two machines, one with a
> cleanly created and encrypted profile and I get the same message.
>
> Windows Defender Version: 1.1.1051.0
> Engine Version: 1.1.1303.0
> Signature Version: 1.14.1361.6
>
> System Information report written at: 04/05/06 06:55:31
> System Name: VALKYRIE
> [System Summary]
>
> Item Value
> OS Name Microsoft Windows XP Professional
> Version 5.1.2600 Service Pack 2 Build 2600
> OS Manufacturer Microsoft Corporation
> System Name VALKYRIE
> System Manufacturer Motion Computing
> System Model LE1600
> System Type X86-based PC
> Processor x86 Family 6 Model 13 Stepping 8 GenuineIntel ~1500 Mhz
> BIOS Version/Date Motion Computing - LE1600 A06, 1/18/2006
> SMBIOS Version 2.34
> Windows Directory C:\WINDOWS
> System Directory C:\WINDOWS\system32
> Boot Device \Device\HarddiskVolume1
> Locale United States
> Hardware Abstraction Layer Version = "5.1.2600.2180
> (xpsp_sp2_rtm.040803-2158)"
> User Name VALKYRIE\Aaron
> Time Zone Eastern Standard Time
> Total Physical Memory 1,536.00 MB
> Available Physical Memory 911.30 MB
> Total Virtual Memory 2.00 GB
> Available Virtual Memory 1.96 GB
> Page File Space 2.29 GB
> Page File C:\pagefile.sys
>

Thanks for the post Aaron. I'm not sure what, if anything, can be done
about this--but you've done a great job of laying out the steps to reproduce
what you are seeing.

--

"Aaron Oneal" <(E-Mail Removed)> wrote in message
news:E422B5A8-8D80-4724-AE4D-(E-Mail Removed)...
>I have used TrueCrypt (www.truecrypt.org) to encrypt my user profile and
> data. Windows Defender chugs along fine until it tries to read HKCU, then
> it
> gets the 0x8050800c error. If I use a non-encrypted profile to run WD, it
> works fine. I am certain my profile is not corrupted as some have
> suggested
> this could cause the error. I've tried this on two machines, one with a
> cleanly created and encrypted profile and I get the same message.
>
> Windows Defender Version: 1.1.1051.0
> Engine Version: 1.1.1303.0
> Signature Version: 1.14.1361.6
>
> System Information report written at: 04/05/06 06:55:31
> System Name: VALKYRIE
> [System Summary]
>
> Item Value
> OS Name Microsoft Windows XP Professional
> Version 5.1.2600 Service Pack 2 Build 2600
> OS Manufacturer Microsoft Corporation
> System Name VALKYRIE
> System Manufacturer Motion Computing
> System Model LE1600
> System Type X86-based PC
> Processor x86 Family 6 Model 13 Stepping 8 GenuineIntel ~1500 Mhz
> BIOS Version/Date Motion Computing - LE1600 A06, 1/18/2006
> SMBIOS Version 2.34
> Windows Directory C:\WINDOWS
> System Directory C:\WINDOWS\system32
> Boot Device \Device\HarddiskVolume1
> Locale United States
> Hardware Abstraction Layer Version = "5.1.2600.2180
> (xpsp_sp2_rtm.040803-2158)"
> User Name VALKYRIE\Aaron
> Time Zone Eastern Standard Time
> Total Physical Memory 1,536.00 MB
> Available Physical Memory 911.30 MB
> Total Virtual Memory 2.00 GB
> Available Virtual Memory 1.96 GB
> Page File Space 2.29 GB
> Page File C:\pagefile.sys
>

It seems to me that WD might be reading the registry in some non-standard
way, though I can't imagine what that might be. It's a shame though, because
I was really looking forward to the WD release. I hope a solution can be
found before the final build. More and more people are using encryption
solutions these days, so TrueCrypt might not be the only one that WD is
incompatible with.

One other thing I should mention, my profile is also an NTFS junction point,
so it's possible it's the junction point and not the encryption causing the
problem. I haven't had the opportunity to test this yet though with an
unencrypted junction point. Just to clarify, my profile is on drive U: and
then I've set up a junction at C:\Documents and Settings\Aaron to point to U:.

"Bill Sanderson MVP" wrote:

> Thanks for the post Aaron. I'm not sure what, if anything, can be done
> about this--but you've done a great job of laying out the steps to reproduce
> what you are seeing.

Here's a little more info. It seems the error occurs when it hits any
registry entries having to do with WinVNC. I suspect WD is trying to issue a
spyware warning and something is causing it to barf. Apparently it can scan
the registry just fine, but it's the detection of a potential spyware
application that's triggering the problem.

"Aaron Oneal" wrote:

> It seems to me that WD might be reading the registry in some non-standard
> way, though I can't imagine what that might be. It's a shame though, because
> I was really looking forward to the WD release. I hope a solution can be
> found before the final build. More and more people are using encryption
> solutions these days, so TrueCrypt might not be the only one that WD is
> incompatible with.
>
> One other thing I should mention, my profile is also an NTFS junction point,
> so it's possible it's the junction point and not the encryption causing the
> problem. I haven't had the opportunity to test this yet though with an
> unencrypted junction point. Just to clarify, my profile is on drive U: and
> then I've set up a junction at C:\Documents and Settings\Aaron to point to U:.

I think I recall one or more other bugs in this beta related to junction
points--however, I thought they were in beta1.

Thanks for passing this on. I know your messages are getting read.
--

"Aaron Oneal" <(E-Mail Removed)> wrote in message
news:EAF9159B-6D6E-467B-BEBD-(E-Mail Removed)...
> Here's a little more info. It seems the error occurs when it hits any
> registry entries having to do with WinVNC. I suspect WD is trying to
> issue a
> spyware warning and something is causing it to barf. Apparently it can
> scan
> the registry just fine, but it's the detection of a potential spyware
> application that's triggering the problem.
>
> "Aaron Oneal" wrote:
>
>> It seems to me that WD might be reading the registry in some non-standard
>> way, though I can't imagine what that might be. It's a shame though,
>> because
>> I was really looking forward to the WD release. I hope a solution can be
>> found before the final build. More and more people are using encryption
>> solutions these days, so TrueCrypt might not be the only one that WD is
>> incompatible with.
>>
>> One other thing I should mention, my profile is also an NTFS junction
>> point,
>> so it's possible it's the junction point and not the encryption causing
>> the
>> problem. I haven't had the opportunity to test this yet though with an
>> unencrypted junction point. Just to clarify, my profile is on drive U:
>> and
>> then I've set up a junction at C:\Documents and Settings\Aaron to point
>> to U:.

Hi Aaron.

Just wanted to let you know that we were able to debug this with the help of
the very useful information you provided below and have implemented a fix
that will go out with the next engine release (probably early next month.)

Thanks for your patience and your excellent problem description. The issue
was not related to the junction point you mentioned, but rather to the
encryption software you are using, and actually was a more general problem
that could happen with other third party file system drivers as well, if the
user profile is stored on a volume that requires the third party file system
driver to access.

Unfortunately there is no work-around with the current engine other than
moving your profile to a volume that is not protected by TrueCrypt, but once
the new engine build is released you should no longer see this error.

Thanks again

-Mike

"Aaron Oneal" <(E-Mail Removed)> wrote in message
news:E422B5A8-8D80-4724-AE4D-(E-Mail Removed)...
>I have used TrueCrypt (www.truecrypt.org) to encrypt my user profile and
> data. Windows Defender chugs along fine until it tries to read HKCU, then
> it
> gets the 0x8050800c error. If I use a non-encrypted profile to run WD, it
> works fine. I am certain my profile is not corrupted as some have
> suggested
> this could cause the error. I've tried this on two machines, one with a
> cleanly created and encrypted profile and I get the same message.
>
> Windows Defender Version: 1.1.1051.0
> Engine Version: 1.1.1303.0
> Signature Version: 1.14.1361.6
>
> System Information report written at: 04/05/06 06:55:31
> System Name: VALKYRIE
> [System Summary]
>
> Item Value
> OS Name Microsoft Windows XP Professional
> Version 5.1.2600 Service Pack 2 Build 2600
> OS Manufacturer Microsoft Corporation
> System Name VALKYRIE
> System Manufacturer Motion Computing
> System Model LE1600
> System Type X86-based PC
> Processor x86 Family 6 Model 13 Stepping 8 GenuineIntel ~1500 Mhz
> BIOS Version/Date Motion Computing - LE1600 A06, 1/18/2006
> SMBIOS Version 2.34
> Windows Directory C:\WINDOWS
> System Directory C:\WINDOWS\system32
> Boot Device \Device\HarddiskVolume1
> Locale United States
> Hardware Abstraction Layer Version = "5.1.2600.2180
> (xpsp_sp2_rtm.040803-2158)"
> User Name VALKYRIE\Aaron
> Time Zone Eastern Standard Time
> Total Physical Memory 1,536.00 MB
> Available Physical Memory 911.30 MB
> Total Virtual Memory 2.00 GB
> Available Virtual Memory 1.96 GB
> Page File Space 2.29 GB
> Page File C:\pagefile.sys
>

Thanks Mike, that's great to hear, and I appreciate you taking the time to
explain. I'm glad I was able to help bring that one to light before release
and I look forward to future builds.

"Mike Treit [Msft]" wrote:

> Hi Aaron.
>
> Just wanted to let you know that we were able to debug this with the help of
> the very useful information you provided below and have implemented a fix
> that will go out with the next engine release (probably early next month.)
>
> Thanks for your patience and your excellent problem description. The issue
> was not related to the junction point you mentioned, but rather to the
> encryption software you are using, and actually was a more general problem
> that could happen with other third party file system drivers as well, if the
> user profile is stored on a volume that requires the third party file system
> driver to access.
>
> Unfortunately there is no work-around with the current engine other than
> moving your profile to a volume that is not protected by TrueCrypt, but once
> the new engine build is released you should no longer see this error.
>
> Thanks again
>
> -Mike
>