marc2003

yes. doesn't even need a restart. one minute rename doesn't work.... import the reg file and it works immediately.

i've just been comparing that reg file to my x86 version and it's identical from what i can see - i haven't checked every line but i've checked as much as i can fit on screen when they're side by side at the start and the end of the file. and it worked straight away - didn't have to re-install the updates. just imported the file and bingo.

well i vlite-d my disk at least 3 months ago if not more. can't remember what version, sorry.... no tweaks and it wasn't unattended. this is what i remember removing system restore windows defender uac indexing/search accessibility options windows sidebar/welcome centre drivers other than that, i left it pretty much as is. i left superfetch alone and didn't disable any other services as far as i can remember.

edited 2 minutes after i posted. the exact change was "puzzled? i bet you are" i changed it to "puzzled? i am. you? anyway, nvm i just won't bother with these updates. my vista flies along without them (thanks to vlite - i am grateful for that)...

hehe. attitude eh? all i said was seemed in inverted commas..... i wish i hadn't bothered.....

right i've just installed a copy of my vlite-d 32bit vista in vmware. competely barebones install. no vmware tools, no software, no drivers. at first i can create/rename folders no problem. but after installing kb937979 x86 it goes wrong as per the original post and my experience. you cannot rename folders.... so it does "seem" to be a direct relation between a vlited install and these updates. puzzled? i am. you? i'm now about to try a clean non-vlite install to see how i get on.

and how is the average user supposed to know that? as most people don't have this problem with the updates, it's obvious you look towards your own setup and what's different about it compared to everyone elses.... and as a vlite user, i also thought the same thing because i have the same problem. ok it's not a vlite problem but you can hardly blame someone for thinking about it.

open regedit. goto hklm\software\microsoft\windows nt\currentversion\winlogon change the value of 'autoadminlogon' to 0. reboot. hope that works for you.