View Full Version : Vista File Protection - Updated 8/30/05
AlphaAlien
11-26-02, 02:02 AM
**UPDATED**
for Vista build 5308.x February CTP
Go into Control Panel and switch to classic view
Browse into Administrative Tools and Local Security Policy
Click on Security Options and Security Options again
Scroll to bottom and disable all the services labeled UAP (User Access Protection)
so where is it?.....heheh jk
Michael
11-26-02, 02:14 AM
hes on 56k takes him a bit to post
AlphaAlien
11-26-02, 02:15 AM
While this is essentially the same way as protection was in XP, the folder with the protected directories\files is finicky about showing up, which is why it took me an extra day to find it. But it works fine when manually typing in the folder through run :) .
Step 1: in explorer go into Tools\Folder Options and make it so it'll show hidden and protected files.
Step2: Goto Start\Run and type in %windir%\system32\restore (after this it's the same as XP)
Step3: right click on filelist.xml and goto it's properties and uncheck read only.
Step4: right click on filelist.xml again and open with notepad.
Step5: You'll see a big list of folders and files here. To remove a file or folder from the graces of windows file protection just ad this:
Files-
<PCHealthProtect>
<VERSION>1.0</VERSION>
<DEFTYPE>E</DEFTYPE>
<FILES>
<Exclude>
<REC>%windir%\foldername\filename.xxx</REC>
</Exclude>
Folders-
<DIRECTORIES>
<Exclude>
<REC>%windir%\foldername</REC>
</Exclude>
*you can ad %windir% itself but it'll only effect %windir% itself not the other folders in it's tree*
After that save it and protection on that file or folder will be gone. But that doesn't mean windows won't still replace edited files. So onto the 2nd part of this how-to.
Step1: Go into %windir%\system32\dllcache and delete the entire contents of the folder, but not the folder itself. Remember if you want a back-up just make a copy of the original system file before editing it.
Step2: Longhorn ad's a new layer to windows file protection in the form of back-up mui's, though not all mui's are back-up's enough are to make it irritating at times. So before you edit a system file do a search for filename.* to make sure their isn't a .mui back-up for it, but be careful their are .mui's with the same name as a file but aren't back-up's so check the file sizes against each other, if they're the same size then the .mui is a back-up if not then it just shares the name.
AlphaAlien
11-26-02, 02:17 AM
also had to write it, and correct it when it didn't like me using protected characters
Originally posted by AlphaAlien
also had to write it, and correct it when it didn't like me using protected characters
thats why it took so long..... :)
couln't you start a thread in another forum and move it when its ready though?
AlphaAlien
11-26-02, 02:24 AM
could but it only took like 12min to write and correct it
Mowzeror
11-26-02, 02:28 AM
*The muis files should be gone when longhorn ships
They are mostly used by programmers and developers to help keep track of changes and such and give easy implementation.
AlphaAlien
11-26-02, 02:40 AM
the mui for shell32 and plex are back-ups, didn't bother checking many more, but enough are back-up's windows used for replacement for it to be noteworthy
KingShip
01-23-03, 04:35 AM
You know, I go through the forums, your like one of the first, to disable WFP in LongHorn !
Before I joined I had disabled it, the same way I do with Windows XP, and it's great to see that it's published, here.
If you know what to remove, it's also a bonus, tho for a first timer disabling WFP, NOT RECOMMENDED.
Oh, and sfcdisable in the reg having all four options, here posted for users, is awesome {:-)
Later KingShip
P.S. Keep up the good work
bobbyrabbit
07-02-03, 08:18 AM
Is the file protection to do with, when you load a certain program, there's a point where it has problems locating a .dll file. If so this is the only reason I went back to using XP. If this is a workaround then I will return to using 4015 as I found it really quite stable.
Also had a problem loading some soundcard drivers, but I guess Xp compatibility mode deals with that?
Thanks for a great forum
AlphaAlien
07-02-03, 03:46 PM
no, windows file protection is what blocks you from editing or replacing core os files and is annoying if you want to replace things.
try 4008 it doesn't have the problems 4015 has.
And using the newest XP drivers and installing in xp compat mode does normally fix those errors.
were can i download longhorn
Michael
01-26-04, 09:28 PM
bad mikey :P ;)
GCNaddict
05-21-05, 12:15 AM
I guess everyone knows already (this topic is older than 5048) but 5048 doesnt have WFP :)
AlphaAlien
05-21-05, 01:03 AM
this stuff was posted at 11-25-02, 11:02 PM ie. end of 2002.Was for 3683
AlphaAlien
08-30-05, 07:03 AM
updated first post :)
VeraBlue
08-30-05, 02:43 PM
Good to know, thanks :).
That guy...
03-14-06, 02:54 AM
hey can you figure something out for beta 2 as well Build 5308 I am completely dumbfounded lol... definetely doesn't work teh same way as beta 1... Trusted Installers doesn't even exist??
AlphaAlien
03-14-06, 03:00 AM
5308 isn't beta 2 -updated first post