You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Vista Home Basic Error 1606 %PUBLIC%\Desktop\

microsoft.public.windows.vista.file management

I've recently had Norton Anti-virus 2009 and when i went to get my live
updates 3 of them wouldn't install.
I wasnt too worried about this because i figured i'd uninstall it and
re-install it to see if it fixes the errors.
Instead of this being an easy task before it would finish updating i
kept getting this error %PUBLIC%\Desktop\

i decided to get rid of Norton and use Avast because i dont have time
to fool around, but now the problem has come back, and its stopping me
from installing Windows Microsoft Office.
I cant run it from the disk so i opened the setup.exe folder as an
admin to run it and i keep getting the Error: 1606 %PUBLIC%\Desktop\
message/
i cant find anything on it and all the forums i do find are for XP.

I'm also having trouble with my desktop because i cant rename my
folders.
If i change the name it'll automatically switch back.
If i create a new folder and try to change the name it wont let me
either.
It'll either switch back to New Folder or it'll say that folder name
that i create doesnt exist.

Id appreciate it if anyone could help me
or if you know of any other sites with info related to my issue

Hello everyone,
Well, I have returned to post my results after searching for a solution
for hours and finally arriving to one that was specific to my
problem....and I decided to share with others experiencing a similar
problem.

I had a similar problem....It took a couple of hours of searching but I
followed the instructions located here
'_http://support.microsoft.com/kb/886549/_'
(http://support.microsoft.com/kb/886549/) on a microsoft support page
and so far the problem has been fixed.