Jump to content

Recommended Posts

Posted

I was looking around to see if there was a way to turn off WFP on windows sp3. I look all over the net but didnt really find anything so I took a crack at it.

I found a way that works for me but would like some other people to try it out.

Step 1

Open run and type regedit and click ok

Step 2

Click edit and go down to Find and click it

Step 3

add this to the Find What box {F750E6C3-38EE-11D1-85E5-00C04FC295EE}

Step 4

Right click on $dll and click modify and replace WINTRUST.DLL with WINTRUST.DLL.old

Step 5

Click edit and go down to find next and click it

Step 6

Repeat Step 4 for each {F750E6C3-38EE-11D1-85E5-00C04FC295EE} "theres about 7 or 8 of them I think"

Step 7

log off or restart pc

Step 8

search for the file you want to replace and make sure you have expanded - includes all files and folders click in the search options

Lets say you searched for sysdm.cpl and wanted to replace it

Step 9

Your search show you that the file is in 2 places

C:\WINDOWS\system32\dllcache\sysdm.cpl and C:\WINDOWS\system32\sysdm.cpl

go to C:\WINDOWS\system32\dllcache and delete sysdm.cpl

Step 10

go to C:\WINDOWS\system32\sysdm.cpl and rename it C:\WINDOWS\system32\sysdm.cpl.old

and drop or copy your sysdm.cpl

Step 11

go to C:\WINDOWS\system32\dllcache and drop or copy your sysdm.cpl there

Step 12

log off or restart your pc

So that worked for me with a few WFP files but I would like some other people to test this out

and I would really like to see if some one could try this on computer that is not patched for themes

It would cool if someone took a patched uxtheme.dll and copied it to a not patched xp sp3 and see

if it works =)

Well let me know if it works for any of you guys

Thanks


Posted (edited)

WFP is already solved on XP SP3.

But your find has great potential for disabling annoying driver signing check (which is performed even if driver signing policy is set to silently succeed).

!!!BUT!!! it also has a great potential for trashing one's windows installation if something goes wrong or if the caller of Wintrust.dll functions doesn't fall back gracefully. A lot more testing is needed.

GL

* Edit - and one must hope the dll doesn't re-register itself. Also, I think deleting it is out of question.

Edited by GrofLuigi

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...