AntiWPA Forum

Hello,

I made an improvement to the Terminal Services Patch v1.3 and I'am naming it v1.4

There are 3 improvements:
1) The patch no longer triggers the Windows File Protection (WFP) warning.
2) The patch no longer has to be executed from %systemRoot%\system32
3) A new key (AllowRemoteRPC) is added to the Registry, see the URL below:
http://www.pcreview.co.uk/forums/thread-2395421.php

QUESTION: Should I upload it somewhere else besides attaching it to this message ?

Please post some feedback, how the patch is working for you.

Works fine, w2k3 r2 sp2, although avg detected the wfpdeprotect.exe as Win32/heur, just clicked ignore meh..., at least the system rebooted ^^ and i can log so many at once! hurray!

getting serious, worked as expected.

Will definitely post the feedback once I try it

There's a download section in AntiWPA but the TS patch is only 1.3, perhaps u can ask the moderator to upload your version

Thanks

Can I ask what this patch does exactly? - Am I right in thinking that it will enable me to run a terminal server on Windows 2003 Server and not need to provide a License server on the network but will enable as many RDP connections to the terminal server in Application mode as possible?

Or will I still need to have an activated license server on the network??

Thanks guys,
Hope to hear from you soon,
Regards, Bobby

Should I upload it somewhere else besides attaching it to this message ?

I added it to the TS 1.3 post so now we have both

So where is the location for the download ? I tried http://antiwpa.freehostplace.com/Other but it's not there

netkepala wrote:So where is the location for the download ? I tried http://antiwpa.freehostplace.com/Other but it's not there

On the front page of this form
viewforum.php?f=11

Is there a way for domain computers to keep the changes made that this patch has made?
Because I always have to reapply the patch when the computer has been rebooted.
And taking this computer out of the domain isn't an option.

Thanks

Perhaps you have the SFC.EXE /SCANBOOT command somewhere in the login script.

If yes, then remove it from the script.
Also execute SFC.EXE /REVERT or use the attached REG file to disable the bootime SFC scanning.

Please let us know if it helped.

Ryanx0r wrote:Is there a way for domain computers to keep the changes made that this patch has made?
Because I always have to reapply the patch when the computer has been rebooted.

good...works fine in w2k3 r2 sp2
thanks

wfpdeprotect is tagged as TR/Crypt.XPACK.Gen by my AV.

So I went the author's website and DL'd the lastest version that did NOT set off alarms.

Perhaps you could re-package this without the suspicious file?

Link is broken... Where can i download?

Thanks

my antivirus said it was a hacktool and put it in the quarantine. I hope it didn't try to repair (corrupt) the file. If so I am sure I have another copy somewhere buried in a backup.

Hello,

I have XP x86 SP3 TermSrvNoRestrPatch-1-3_PreDbgFix1. (Local IP 192.168.0.1)
All works well, multiple connections to the same user, remote control are OK...
I just have a little problem with the administrative share (on the network).

I can RDP to this computers with the same account. Connect to all the
administrative shares (C$,D$,Admin$) locally or on "RDP session to this computers" : In explorer \\192.168.0.1\c$ --> Ok locally or on "RDP session to this computers".

But these commands do not work on network : if i use another PC (ex 192.168.0.2 and In explorer \\192.168.0.1\c$ --> KO) problem with the administrative share (on the network).

I tried adding (found in Terminal Server Patch v1.4) :
hklm\SYSTEM\CurrentControlSet\Control\Terminal Server
AllowRemoteRPC
reg_dword 1

But it's always the same

Is there a solution ?

Ok i found :

HKLM\System\CurrentControlSet\Control\LSA
ForceGuest
reg_dword 0

TerminalServicesPatch_v1.4.rar works like a charm on XP

viewtopic.php?f=4&t=1120#p7595

Hello,

Thanks for this great patch and keep the work
Works perfectly on Windows 2003 x86 SP2 french ^^

++