Brad, when you package on a machine with several drives, the error you subscribe appears to be a driveletter mallfunction.

Go to drive management, and give your USB stick a higher drive letter.
It also happens in layers that are build by using global capture. If you package a application form a usb device, the dll is touched and gets in the layer.

Regards
Erik
www.dvs4sbc.nl

Erikw, thanks for your feedback, however, I don't believe this is what I'm dealing with. It doesn't happen every time but when it does, the layers (all of them) have to be either reset or deactivated and reactivated before the USB drive will work. The USB drive can be plugged in and the link light will turn on but the drive doesn't show up anywhere, even in the disk management. The machine I create layers on only has the basic drives. A, C, D.

Try booting up the system with no autoactivated layers.
Activate your layers.
Insert the stick.
then deactivate all your layers.
If the stick disappears you have a wrong DlL in one of the layers.

Second step should be a post of all the exclusions you have.
A lot of odd errors appear when you have strange exclusions.

Regards
Erik
www.dvs4sbc.nl

I've noticed that in the software world, tech problems tend to come in threes (like celebrity deaths!). So, since this Microsoft KB article recently restored the use of my USB devices, and since a coworker just had the same problem last week... I'm seriously wondering if this isn't your problem as well: http://support.microsoft.com/kb/314060/en-us

I had those keys that they tell you delete, in a couple of my layers (one of them was Winamp, don't recall the other). Not sure how they got there, but after deleting them, all is golden again with my USB drives! So it wasn't strictly speaking an SVS issue -- the offending reg entries just happened to be in layers.

Scott Jones
Product Manager
Symantec