Aaron Klotz
Aaron Klotz
The `ERROR_INVALID_PARAMETER` error from `VirtualAlloc` is because the base address is too high. The allocation needs to fit within the minimum and maximum application addresses as provided by `GetSystemInfo`.
Not off the top of my head, but I'll do some spelunking and see what I can come up with.
@DentonGentry Here's a shot in the dark, but what the hell: I took a look a that pcap. I noticed that shortly after the delay there's some activity surrounding detection...
Wasn't the main issue some cgo stuff?
The first bullet (for the number of times background content processes have been killed) was already landed as part of #17864, so this issue only needs to deal with the...
(I have a pending PR for walk that depends on this)
Since we do not yet know the root cause as to how we ended up in this situation, I'd rather we did not close this issue. I did a bit...
I will also look into capturing logs for this in future client releases.
Re: different behaviour depending on whether or not we're on Windows Server: In the general case I think this scheme makes sense. The only thing I'd point out is that...
Here's the human-readable form of that SDDL: ``` PS C:\Users\dblohm7> ConvertFrom-SddlString -Sddl "O:BAG:BAD:PAI(A;OICI;GWGR;;;BU)(A;OICI;GWGR;;;SY)" Owner : BUILTIN\Administrators Group : BUILTIN\Administrators DiscretionaryAcl : {NT AUTHORITY\SYSTEM: AccessAllowed (GenericRead, GenericWrite), BUILTIN\Users: AccessAllowed (GenericRead, GenericWrite)}...