Talk:Kernel Patch Protection
|This article is of interest to the following WikiProjects:|
|To-do list for Kernel Patch Protection:|
"Some instances of"
I removed the phrase "Some instances of" because I think it is confusing and somewhat misleading. The KPP FAQ states
- "The Windows kernel is tested extensively before any release of the operating system to ensure a high level of quality."
And again, from Scott Field:
- "The kernel is the most carefully coded piece of the entire operating system...The BSoD is bad, so we want to do everything we can to keep customers from seeing it."
In other words, it is highly unlikely that a Blue Screen of Death error is going to come from Microsoft code. It is much more likely that the error came from unsupported patching. But even so, the current way the point is phrased,
- "The Blue Screen of Death, which results from serious errors in the kernel"
KAV kernel patching
I changed the remarks about KAV not patching the kernel to reflect the state of their software in June 2006. The original citations were only for Sophos and didn't even mention KAV, so I am not sure how KAV got mentioned as not patching the kernel. There is an article describing them doing so which is now cited by the page in the place of the old (and as far as I can tell inaccurate) statement. Skywing 02:16, 22 September 2007 (UTC)
- OK, thanks for the fix. I don't know what I was thinking when I included Kaspersky in that statement. —Remember the dot (talk) 03:23, 22 September 2007 (UTC)
"The Blue Screen of Death, which results from serious errors in the kernel."
Drivers/programs that are trying to patch the kernel will cause the system to crash instantly. Without the protection the system would go on smoothly. —Preceding unsigned comment added by 184.108.40.206 (talk) 14:35, 26 January 2009 (UTC)
- Go on smoothly installing a rootkit? The idea is that with PatchGuard, the system crashes before the kernel patch can do any real damage. Kernel patches of all sources are notorious for causing security, stability, and performance problems. —Remember the dot (talk) 19:37, 26 January 2009 (UTC)
I would argue that KPP is an idea towards Microkernel without actually having a microkernel architecture. As AMD64 supports four privilege levels and therefore true native microkernel implementation, it's IMHO a bad idea at all. --220.127.116.11 (talk) 19:18, 24 April 2015 (UTC)
Do know if this is on the 64 bit of XP? That's what I have but somehow my friend patched my kernel I think. Or is it because they don't force you to run in test mode (DRM issues with unsigned drivers)? I know it was introduced in Server 2003, but I'm not sure about XP. 18.104.22.168 (talk) 05:44, 5 October 2009 (UTC)
Hello fellow Wikipedians,
I have just modified 4 external links on Kernel Patch Protection. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Corrected formatting/usage for http://www2.grisoft.com/doc/324/us/crp/3
- Added archive https://web.archive.org/web/20070217053224/http://www.windows-now.com:80/blogs/robert/archive/2006/08/12/PatchGuard-and-Symantecs-Complaints-About-Windows-Vista.aspx to http://www.windows-now.com/blogs/robert/archive/2006/08/12/PatchGuard-and-Symantecs-Complaints-About-Windows-Vista.aspx
- Added archive https://web.archive.org/web/20061124094344/http://blogs.msdn.com:80/windowsvistasecurity/archive/2006/08/11/695993.aspx to http://blogs.msdn.com/windowsvistasecurity/archive/2006/08/11/695993.aspx
- Added archive https://web.archive.org/web/20070205155710/http://www.microsoft.com:80/security/windowsvista/allchin.mspx to http://www.microsoft.com/security/windowsvista/allchin.mspx
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
You may set the
|checked=, on this template, to true or failed to let other editors know you reviewed the change. If you find any errors, please use the tools below to fix them or call an editor by setting
|needhelp= to your help request.
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
If you are unable to use these tools, you may set
|needhelp=<your help request> on this template to request help from an experienced user. Please include details about your problem, to help other editors.