borjazd Posted September 27, 2009 Posted September 27, 2009 (edited) Hello everybody, I installed a vLited vista home premium x64, and everything goes perfect except the folder view's configuration. I have the "remember each folder's view settings" option checked, and i don't know why it happensthe cause could be a removed component?Which component I DON'T have to remove to prevent this?thanks a lotBorjazd Edited September 27, 2009 by borjazd
redxii Posted September 27, 2009 Posted September 27, 2009 I have this problem w/ 32-bit, somehow removing Welcome Center fixes the problem.
borjazd Posted September 27, 2009 Author Posted September 27, 2009 (edited) So, we can solve this problem removing Welcome Center or keeping it? Edited September 27, 2009 by borjazd
redxii Posted September 28, 2009 Posted September 28, 2009 Try removing it if you haven't already. There are also numerous websites with details on how to fix it, since it's a Vista problem, to avoid reinstalling.
borjazd Posted September 28, 2009 Author Posted September 28, 2009 (edited) yes, i have "Welcome Center" already removed.i tried all the fixes i found by the internet, at the begining i can solve the problem, but few days later the O.S. forgot again folder's configuration, so i was wondering it could be a removed component, but i don't know which i'm desperated and hope if someone can help methanks Edited September 28, 2009 by borjazd
hclarkjr Posted September 28, 2009 Posted September 28, 2009 i have vista ultimate 64 bit that i used vlite on and have no problems at all with my folders. what service pack are you using? i believe service pack 2 fixes the folder issue. also look here for solution to your problem http://www.annoyances.org/exec/show/choosetemplate
borjazd Posted September 29, 2009 Author Posted September 29, 2009 thanks a lot, i will try this method... i hope this could finally solve this issue, i will know the answer 3 or 4 days lateri'll tell youbye
Ultimist Posted October 2, 2009 Posted October 2, 2009 Welcome Center may not be the problem, though. I removed it as part of the build, and yet I still have this same problem.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now