That's some great info GrofLuigi! You figured it out. The first file you mentioned, fltmgr.sys (FS Filter Manager), is a new service which came with SP2. From what I can read about it, you don't really need this at all. You can easily disable it like this; REGEDIT4 ; Stop the service from running [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FltMgr] "Start"=dword:00000004 ; ..or remove FS Filter Manager alltogether :) [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FltMgr] The main problem however, is the Mount Manager (mountmgr.sys) There's two places you need to hack/alter in the file if you want to get rid of the automaticly creating of the SIV\MountPointManagerRemoteDatabase file, 0A10: 5C 00 53 00 79 00 73 00 (...) 9610: 6C 43 72 65 61 74 65 53 (...) But since I'm not a hacker, I wasn't able to successfully to make it work as I wanted. I was able to disbale the creation of the mountpoint(..) file by changing the first of the mentioned addresses of (0A10) 5C 00 53(...) to 5C 00 3F(..) But I was unable to change the automatic creation of the SIV folder, which I think is programmed into the second address (9610). When I tried to change that, I couldn't launch into Windows, bummer I'll leave the hacking to someone who knows what they're doing. However, you can make it work by replacing the mountmgr.sys file, with the pre-SP2 Build, which dosen't contain any aforementioned "always-create-crappy-files-on-my-drive" code as far as I can see. I found my original XP CD, and copied mountmgr.sys (Build 5.1.2600.0) to my Windows\System32\Drivers\ folder, and restarted the machine. I deleted the System Voulme Information folder and have been running my machine for 17 hours. I've also restarted the machine 2-3 times to check if the folder gets back, and it surely does not. It's working like it used to under SP1 I won't reccomend doing any of this, unless you know what you're doing and are willing to take some risks. For your convinience, here's the original pre-SP2 Build 5.1.2600.0 of mountmgr.sys Click here