Let me guess you made a windows update recently...
It happend to me also, on another thread I wrote the item on win update that caused the problem, take a look at:
http://www.litestep.net/index.php?section=4&action=view&catId=1&id=804

And by the way, it has nothing to do with litestep (I believe it also happens when running explorer as shell also)