Re:Microsoft no longer signs Windows drivers for Process Hacker
by Daedren on Sunday October 24, 2021 @05:50AM
(#28976344)
Yes, it's Special Administration Console.
Re:Microsoft no longer signs Windows drivers for Process Hacker
by heavyset_go on Sunday October 24, 2021 @05:11AM
(#28976131)
Not sure, I'm quoting directly from the article.
Re:Microsoft no longer signs Windows drivers for Process Hacker
by y4mi on Sunday October 24, 2021 @05:41AM
(#28976296)
The same question has been answered in the linked GitHub issue, though the comment was marked as off topic.
It's special administrative console, more in depth info what that actually is in the comment.
https://github.com/processhacker/processhacker/discussions/7...
Re:Microsoft no longer signs Windows drivers for Process Hacker
by nitrogen on Sunday October 24, 2021 @04:05PM
(#28981391)
The highlighted comment has been marked as off-topic and requires logging in to view, which I'm disinclined to do from mobile. Is there a summary elsewhere?
Re:Microsoft no longer signs Windows drivers for Process Hacker
by pitay on Tuesday October 26, 2021 @06:47AM
(#28998691)
Here you go:
DavidXanatos
on 16 Aug
Interesting driver,
is the process termination feature of PH the only thing MSFT has a problem with?
I mean if its the only thing they don't like, may be its worth moving that feature into a separate tool or a plugin with an own unsigned driver?
Also changing the name would be an option, if than all the problems can be avoided.
@dmex
dmex
on 16 Aug
Maintainer
the only thing MSFT has a problem with
MS refused to discuss anything and have ignored every email so who knows what their problem is.
if its the only thing they don't like
It's not the only thing.... There are recent changes to APIs that block and limit features when the caller isn't taskmgr.exe.
Either way this discussion is offtopic from the KPH updates.
do you mean Special administration console? or Semi-annual channel?