FYI: The pre-release definitions will solve the problem.
Article updated: UPDATE: I'm also being told (thanks <https://urldefense.proofpoint.com/v1/url?u=http://twitter.com/%40bartsurminski&k=7DHVT22D9IhC0F3WohFMBA%3D%3D%0A&r=KpxLqbtgDLBMJ7jB3bRYJp4LcYL%2BHWg%2BAJWVqh6JKCQ%3D%0A&m=YRiTAHy%2FfyzJuuIHMzEJ5fbeW2MeT%2B3vjgrv99rG2%2BA%3D%0A&s=fc4cc2dc2763e5228822603ccbd9c006260b94584672cd51322ae44f183cfadd> Bart Surminski!) that a beta version of the definition will also fix this. You can download the definition beta here: <https://urldefense.proofpoint.com/v1/url?u=http://support.microsoft.com/kb/939757&k=7DHVT22D9IhC0F3WohFMBA%3D%3D%0A&r=KpxLqbtgDLBMJ7jB3bRYJp4LcYL%2BHWg%2BAJWVqh6JKCQ%3D%0A&m=YRiTAHy%2FfyzJuuIHMzEJ5fbeW2MeT%2B3vjgrv99rG2%2BA%3D%0A&s=6d2ee9e2b2bb4751cd2d2b1d0a194bd2a1c7bafa6035f986752756d96f623972> https://urldefense.proofpoint.com/v1/url?u=http://support.microsoft.com/kb/939757&k=7DHVT22D9IhC0F3WohFMBA%3D%3D%0A&r=KpxLqbtgDLBMJ7jB3bRYJp4LcYL%2BHWg%2BAJWVqh6JKCQ%3D%0A&m=YRiTAHy%2FfyzJuuIHMzEJ5fbeW2MeT%2B3vjgrv99rG2%2BA%3D%0A&s=6d2ee9e2b2bb4751cd2d2b1d0a194bd2a1c7bafa6035f986752756d96f623972. Latest pre-release definition version is 1.171.67.0. You can read more about beta definitions here: Microsoft pre-release definition updates <https://urldefense.proofpoint.com/v1/url?u=http://www.microsoft.com/security/portal/shared/prereleasesignatures.aspx&k=7DHVT22D9IhC0F3WohFMBA%3D%3D%0A&r=KpxLqbtgDLBMJ7jB3bRYJp4LcYL%2BHWg%2BAJWVqh6JKCQ%3D%0A&m=YRiTAHy%2FfyzJuuIHMzEJ5fbeW2MeT%2B3vjgrv99rG2%2BA%3D%0A&s=954d4920d8f39f9df86240a3ef3752aba403211f2990cdcb82051d69b83a59e2> . From: [email protected] [mailto:[email protected]] On Behalf Of Cain, Steven Sent: Wednesday, April 16, 2014 10:48 AM To: [email protected] Subject: RE: [NTSysADM] XP issue after Forefront update What, Server 2003? :) Steve Cain Sr. System Administrator From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rod Trent Sent: Wednesday, April 16, 2014 10:35 AM To: [email protected] <mailto:[email protected]> Subject: RE: [NTSysADM] XP issue after Forefront update An accident brought about by not being required to test on an unsupported OS. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Wednesday, April 16, 2014 10:24 AM To: '[email protected]' Subject: RE: [NTSysADM] XP issue after Forefront update Hmmm, accident, or planned? From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rod Trent Sent: Wednesday, April 16, 2014 7:15 AM To: [email protected] <mailto:[email protected]> Subject: RE: [NTSysADM] XP issue after Forefront update Just got word… https://urldefense.proofpoint.com/v1/url?u=http://windowsitpro.com/windows-xp/windows-xp-hangs-after-latest-forefront-endpoint-protection-update&k=7DHVT22D9IhC0F3WohFMBA%3D%3D%0A&r=KpxLqbtgDLBMJ7jB3bRYJp4LcYL%2BHWg%2BAJWVqh6JKCQ%3D%0A&m=YRiTAHy%2FfyzJuuIHMzEJ5fbeW2MeT%2B3vjgrv99rG2%2BA%3D%0A&s=c1493d3ebd9fb431f230d27178ce5402fbee5950722452673955fc87a6404565 From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Todd Lemmiksoo Sent: Wednesday, April 16, 2014 9:37 AM To: [email protected] <mailto:[email protected]> Subject: Re: [NTSysADM] XP issue after Forefront update The PC's freeze on the login or startup process. On Wed, Apr 16, 2014 at 8:27 AM, Rod Trent <[email protected] <mailto:[email protected]> > wrote: They won’t work at all? Or, just the Endpoint Protection client? From: [email protected] <mailto:[email protected]> [mailto:[email protected] <mailto:[email protected]> ] On Behalf Of Todd Lemmiksoo Sent: Wednesday, April 16, 2014 9:08 AM To: [email protected] <mailto:[email protected]> Subject: [NTSysADM] XP issue after Forefront update After last nights ForeFront update our XP machines will not work. Have anyone else experienced this. -- T. Todd Lemmiksoo -- T. Todd Lemmiksoo
