KB4503327 breaks PPTP

Rollback the update to restore PPTP client connectivity.

Thank you, 73,

--
Don Kuenz KB7RPU
There was a young lady named Bright Whose speed was far faster than light;
She set out one day In a relative way And returned on the previous night.

In article , Don Kuenz, KB7RPU
wrote:

Rollback the update to restore PPTP client connectivity.

pptp is fundamentally broken, making it not secure.

nospam wrote:
In article , Don Kuenz, KB7RPU
wrote:

Rollback the update to restore PPTP client connectivity.

pptp is fundamentally broken, making it not secure.

:%s/pptp/microsoft/g

Don Kuenz, KB7RPU wrote:

Rollback the update to restore PPTP client connectivity.

https://en.wikipedia.org/wiki/Point-...eling_Protocol
"The Point-to-Point Tunneling Protocol (PPTP) is an obsolete method for
implementing virtual private networks. PPTP has many well known security
issues."
Also see the Security section. You'll probably want to use a different
VPN protocol.

https://support.microsoft.com/en-us/...date-kb4503327
Nothing in the "Known issues" section about PPTP.

Is this just your experience with the update, or do you have
substantiating evidence that PPTP will fail with lots of users after
updating? There are more severe problems with the update; see below.

Windows 10 KB4503327 brings black screen issues for many
https://windowsreport.com/kb4503327-black-screen/

VanguardLH wrote:
Don Kuenz, KB7RPU wrote:

Rollback the update to restore PPTP client connectivity.

https://en.wikipedia.org/wiki/Point-...eling_Protocol
"The Point-to-Point Tunneling Protocol (PPTP) is an obsolete method for
implementing virtual private networks. PPTP has many well known security
issues."
Also see the Security section. You'll probably want to use a different
VPN protocol.

https://support.microsoft.com/en-us/...date-kb4503327
Nothing in the "Known issues" section about PPTP.

Is this just your experience with the update, or do you have
substantiating evidence that PPTP will fail with lots of users after
updating? There are more severe problems with the update; see below.

Windows 10 KB4503327 brings black screen issues for many
https://windowsreport.com/kb4503327-black-screen/

W10's first invocation of MsMpEng.exe (Windows Defender Antivirus
Service) on a new PC uses so many resources when it initially runs that
it breaks the PPTP client through starvation of resources. After
approximately 30-60 minutes MsMpEng.exe drops lower on the Task List
and W10's PPTP client starts to work.

This anomaly was originally misdiagnosed and mistakenly attributed to
KB4503327.

In regards to the Black Screen problem, pressing CtrlAltDel often
displays the Task Manager, which can then be used to resolve the issue.
Sometimes displaying the Task Manager is enough, in and of itself to
reveal the Desktop.

Thank you, 73,

--
Don Kuenz KB7RPU
There was a young lady named Bright Whose speed was far faster than light;
She set out one day In a relative way And returned on the previous night.

Don Kuenz, KB7RPU wrote:

VanguardLH wrote:
Don Kuenz, KB7RPU wrote:

Rollback the update to restore PPTP client connectivity.

https://en.wikipedia.org/wiki/Point-...eling_Protocol
"The Point-to-Point Tunneling Protocol (PPTP) is an obsolete method for
implementing virtual private networks. PPTP has many well known security
issues."
Also see the Security section. You'll probably want to use a different
VPN protocol.

https://support.microsoft.com/en-us/...date-kb4503327
Nothing in the "Known issues" section about PPTP.

Is this just your experience with the update, or do you have
substantiating evidence that PPTP will fail with lots of users after
updating? There are more severe problems with the update; see below.

Windows 10 KB4503327 brings black screen issues for many
https://windowsreport.com/kb4503327-black-screen/

W10's first invocation of MsMpEng.exe (Windows Defender Antivirus
Service) on a new PC uses so many resources when it initially runs that
it breaks the PPTP client through starvation of resources. After
approximately 30-60 minutes MsMpEng.exe drops lower on the Task List
and W10's PPTP client starts to work.

This anomaly was originally misdiagnosed and mistakenly attributed to
KB4503327.

In regards to the Black Screen problem, pressing CtrlAltDel often
displays the Task Manager, which can then be used to resolve the issue.
Sometimes displaying the Task Manager is enough, in and of itself to
reveal the Desktop.

Thank you, 73,

Hmm, don't remember ever seeing msmpeng.exe consuming a huge CPU usage
level on starting Windows, or at any time unless I manually instigate a
scan. Even then, its CPU usage goes up to only about 8%. Maybe I've
just been lucky. This is on a workstation (home PC), not as a server.
Do you have more than one anti-virus or other security software that may
conflict or compete with MS Defender?

Are you auto-starting a large transfer of a huge number of files over
the VPN that MS Defender then has to scan to check for malware? Have
you tried running a full scan by MS Defender before you shutdown, so it
doesn't have so many files to scan on Windows startup?

If MS Defender is having to repeatedly scan lots of new files, you might
want to disable its Sample Submission feature. I know some companies
disable this because it poses a privacy issue: their program code might
be detected as malicious and MS Defender uploads it, so now Microsoft
has a copy of proprietary code from the company's Dev group.

While you can set a CPU usage limit on the process (Task Manager,
right-click on a process, select Affinity, set CPU usage), I don't think
that sticks across restarts of the OS. Plus, as I recall, MS Defender
blocks this change to protect itself.

Since PPTP is just a protocol, not a [startup] program or service, just
*what* is using PPTP when you start Windows? If it is a service, you
could reconfigure it for Delayed Start. If it is a startup program, you
could try moving (deleting) it from its current startup location and
define a scheduled event in Task Scheduler with a delayed start.

VanguardLH wrote:
Don Kuenz, KB7RPU wrote:

VanguardLH wrote:
Don Kuenz, KB7RPU wrote:

Rollback the update to restore PPTP client connectivity.

https://en.wikipedia.org/wiki/Point-...eling_Protocol
"The Point-to-Point Tunneling Protocol (PPTP) is an obsolete method for
implementing virtual private networks. PPTP has many well known security
issues."
Also see the Security section. You'll probably want to use a different
VPN protocol.

https://support.microsoft.com/en-us/...date-kb4503327
Nothing in the "Known issues" section about PPTP.

Is this just your experience with the update, or do you have
substantiating evidence that PPTP will fail with lots of users after
updating? There are more severe problems with the update; see below.

Windows 10 KB4503327 brings black screen issues for many
https://windowsreport.com/kb4503327-black-screen/

W10's first invocation of MsMpEng.exe (Windows Defender Antivirus
Service) on a new PC uses so many resources when it initially runs that
it breaks the PPTP client through starvation of resources. After
approximately 30-60 minutes MsMpEng.exe drops lower on the Task List
and W10's PPTP client starts to work.

This anomaly was originally misdiagnosed and mistakenly attributed to
KB4503327.

In regards to the Black Screen problem, pressing CtrlAltDel often
displays the Task Manager, which can then be used to resolve the issue.
Sometimes displaying the Task Manager is enough, in and of itself to
reveal the Desktop.

Hmm, don't remember ever seeing msmpeng.exe consuming a huge CPU usage
level on starting Windows, or at any time unless I manually instigate a
scan. Even then, its CPU usage goes up to only about 8%. Maybe I've
just been lucky. This is on a workstation (home PC), not as a server.
Do you have more than one anti-virus or other security software that may
conflict or compete with MS Defender?

Are you auto-starting a large transfer of a huge number of files over
the VPN that MS Defender then has to scan to check for malware? Have
you tried running a full scan by MS Defender before you shutdown, so it
doesn't have so many files to scan on Windows startup?

If MS Defender is having to repeatedly scan lots of new files, you might
want to disable its Sample Submission feature. I know some companies
disable this because it poses a privacy issue: their program code might
be detected as malicious and MS Defender uploads it, so now Microsoft
has a copy of proprietary code from the company's Dev group.

While you can set a CPU usage limit on the process (Task Manager,
right-click on a process, select Affinity, set CPU usage), I don't think
that sticks across restarts of the OS. Plus, as I recall, MS Defender
blocks this change to protect itself.

Since PPTP is just a protocol, not a [startup] program or service, just
*what* is using PPTP when you start Windows? If it is a service, you
could reconfigure it for Delayed Start. If it is a startup program, you
could try moving (deleting) it from its current startup location and
define a scheduled event in Task Scheduler with a delayed start.

This happened on three brand new W10P PCs fresh out of the box. Brand
new PCs normally settle down after a couple of days of initial updates
when connected to the Inet with the Power set to Always On.
This batch of PCs got rushed into production too fast. MsMpEng.exe
uses 30% - 50% of available CPU cycles when it runs for the first time
on a new PC. It uses so many CPU cycles and so much memory that W10P's
PPTP client software times out because it can not obtain the CPU cycles
nor the memory that it needs. After MsMpEng.exe finishes its initial
scan/download/update/whatever W10P's PPTP client software runs just
fine.

Thank you, 73,

--
Don Kuenz KB7RPU
There was a young lady named Bright Whose speed was far faster than light;
She set out one day In a relative way And returned on the previous night.