>I am mapping and unmapping drives from my application. The mapping portion appears to work fine. I see the drive appear in file explorer. But after Unmapping it, the drive appears with a red X in it. Then if I try mapping the drve again I get a error 1202. Something about attempting to connect but failing because the drive is in use. Is there a way to free up this unmapped drive, so I can use it again?

Why are you mapping drives rather than just using UNC paths to refer to files/folders?

Mapping drives can really piss a user off if you manage to screw up the drives they already had mapped.

I know that's not answering your question - I'm just surprised to see someone still mapping drives for an application.