Alright. I've spent the past while working on this bug. I was in every database, every WP2.0 php file, and tracked everything to everywhere, just to find out how simply stupid this bug actually is. Along the way, I've learned how WP actually works inside and out, its kinda mind boggling. Anyways, here is the quick, simple, stupid fix. in the bottom of the wp-config.php file you'll find this:
017: /* That's all, stop editing! Happy blogging. */
018:
019: define('ABSPATH', dirname(__FILE__).'/');
020: require_once(ABSPATH.'wp-settings.php');
on line 19, change the dirname(__FILE__) to the actual path, and put it in quotation mark. For my server, the change looks like this:
017: /* That's all, stop editing! Happy blogging. */
018:
019: define('ABSPATH', 'w:/www/wordpress'.'/');
020: require_once(ABSPATH.'wp-settings.php');
021: ?>
The reason for this is that on windows, it uses backwards slashes in the file path, to php this looks like its trying to escape caractures. Anyways, I hope this helps out, you'll have to delete the files that you where unable to delete before, as this change will not effect them. Hope this all makes sense, im running on an empty tank 5 hours past my bedtime. - Allan.