#SysInternals

Nacktivnacktiv
2025-12-29

An dieser Stelle sollte ich vielleicht mal 1 Schritt zurücktreten und resümieren, was passiert ist. Die Beiträge waren teils recht kleinteilig, obwohl ich nur das wichtigste notiert habe. Tatsächlich war das eine umfangreiche Analyse mit ++ -z , unter Mithilfe von und Die beiden erzählen leider auch Mist und man muss genau hinschauen, aber ohne sie wäre das kaum machbar gewesen

Nacktivnacktiv
2025-11-21

Der System Monitor soll in Windows 11 integriert werden. techcommunity.microsoft.com/bl
Vielleicht ist das der Grund, dass jetzt hinten runter fällt - schade.

Zurück zu ich habe das mit und diskutiert. Bei ersterem stößt man leider schnell an die Grenzen und dreht sich dann im Kreis. Mit ChatGpt (Basismodell) kann man erstaunlich tief in das Problem eindringen, aber es ist beileibe nicht alles richtig, was das Ding erzählt. Man muss hinschauen!

2025-09-28

quicktipp #103: inspecting the permissions of a named pipe on Windows with sysinternals `accesschk.exe`.

learn.microsoft.com/en-us/sysi

# this is Docker's named pipe on Windows:
# \\.\pipe\docker_engine

# let's display its permissions with
# `accesschk.exe` from http://microsoft.com/sysinternals

# using the `\pipe\<name>` path over `\\.\pipe\<name>`
# avoids opening the pipe, which can cause problems

# compact summary
PS> accesschk.exe -nobanner -accepteula \pipe\docker_engine \\.\Pipe\docker_engine
  RW BUILTIN\Administrators
  RW NT AUTHORITY\SYSTEM
  RW mycomputer\docker-users

# (the gist of it: the `docker_engine` pipe grants ReadWrite permissions to the local Windows group `docker-users`.)

# the exact SDDL  
PS> accesschk.exe -nobanner -accepteula -L \pipe\docker_engine \\.\Pipe\docker_engine_windows
  O:BAD:P(A;;FA;;;BA)(A;;FA;;;SY)(A;;0x12019f;;;S-1-5-21-2792129516-4286106307-505588360-1006)
  
# verbose
PS> C:\tools\accesschk.exe -nobanner -accepteula -lv \pipe\docker_engine_windows\\.\Pipe\docker_engine
  DESCRIPTOR FLAGS:
      [SE_DACL_PRESENT]
      [SE_DACL_PROTECTED]
      [SE_SELF_RELATIVE]
  OWNER: BUILTIN\Administrators
  [0] ACCESS_ALLOWED_ACE_TYPE: BUILTIN\Administrators
        FILE_ALL_ACCESS
  [1] ACCESS_ALLOWED_ACE_TYPE: NT AUTHORITY\SYSTEM
        FILE_ALL_ACCESS
  [2] ACCESS_ALLOWED_ACE_TYPE: mycomputer\docker-users
        FILE_ADD_FILE
        FILE_CREATE_PIPE_INSTANCE
        FILE_APPEND_DATA
        FILE_LIST_DIRECTORY
        FILE_READ_ATTRIBUTES
        FILE_READ_DATA
        FILE_READ_EA
        FILE_WRITE_ATTRIBUTES
        FILE_WRITE_DATA
        FILE_WRITE_EA
[...]
2025-09-22

🖥️ “Big Brother is Watching!” by Bartek Bielawski taught how to troubleshoot client machines remotely using #PowerShell without disrupting users: 🧰 #Sysinternals (Handle, Procmon, RAMMap) 📡 #pktmon > netsh 🧪 Smart prep = zero friction 🎟️ psconf.eu #RemoteSupport #PSConfEU

- YouTube

Yesterday's Roseumbraroze@tech.lgbt
2025-09-05

Oh, finally!

I find it *hella* annoying that #Windows is smart enough to tell me that there's a running program that is keeping me from ejecting a USB disk. ...WITHOUT telling me which bloody program it is.

So apparently, the trick is to use #Sysinternals Process Explorer and use the Find Handle feature.

And the answer is... #Dropbox? Fucking *Dropbox*? I *specifically* told Dropbox to not touch drives. Why would it even be doing that??? What's *wrong* with cloud storage service developers? I swear none of the apps work logically and all of them are janky as f

2025-07-22

🖥️ “Big Brother is Watching!” by Bartek Bielawski taught how to troubleshoot client machines remotely using #PowerShell without disrupting users: 🧰 #Sysinternals (Handle, Procmon, RAMMap) 📡 #pktmon > netsh 🧪 Smart prep = zero friction 🎟️ psconf.eu #RemoteSupport #PSConfEU

- YouTube

Pustam | पुस्तम | পুস্তম🇳🇵pustam_egr@mathstodon.xyz
2025-06-23

Linus Torvalds and Bill Gates Meet for the First Time

In a surprising turn of events, Microsoft co-founder Bill Gates and Linus Torvalds, the creator of the Linux kernel, recently met for the first time. The historic encounter took place at a dinner hosted by Sysinternals' creator Mark Russinovich.

This rare moment brought together icons from Linux and Windows, with Microsoft’s Dave Cutler also meeting Torvalds for the first time. As Russinovich humorously noted in a LinkedIn post, “No major kernel decisions were made.” linkedin.com/posts/markrussino

#Linux #LinuxKernel #Windows #BillGates #Linus #LinusTorvalds #MSFT #Microsoft #Tech #Technology #RareMoment #TechWorld #OperatingSystem #OS #Kernel #Sysinternals #DaveCutler

Alvin Ashcraft 🐿️alvinashcraft@hachyderm.io
2025-02-18

EPISODE 10 - Scott & Mark Learn To... Zoomit with Scott Hanselman & Mark Russinovich | Wed at 12:15pm EST.

youtube.com/watch?v=8WEoZ646Ik

#zoomit #sysinternals #windows #devtools

2025-01-31

#BSI WID-SEC-2025-0231: [NEU] [UNGEPATCHT] [mittel] #Microsoft #SysInternals: Schwachstelle ermöglicht Codeausführung

Ein lokaler Angreifer kann eine Schwachstelle in Microsoft SysInternals ausnutzen, um beliebigen Programmcode auszuführen.

wid.cert-bund.de/portal/wid/se

Alvin Ashcraft 🐿️alvinashcraft@hachyderm.io
2024-12-17

ZoomIt v9.0 from Sysinternals.

This release adds drawing and annotation on top of live windows and the desktop.

techcommunity.microsoft.com/bl
#windows #powerusers #sysinternals #utilities

kurtshkurtsh
2024-12-16

Announcing ZoomIt v9.0 with LiveDraw and LiveZoom

No more freezing before sketching/writing. Now you can write/draw on the Windows desktop & over applications that are actively moving on the screen.

And it's still free! 😁

techcommunity.microsoft.com/bl

Alvin Ashcraft 🐿️alvinashcraft@hachyderm.io
2024-12-10

Premiering tomorrow: EPISODE 6 - Scott & Mark Learn To... Take a Dump.

buff.ly/3ZwJETv
#podcast #devcommunity #programming #productivity #debugging #windowsdev #sysinternals

TiTiNoNero :__:77nn@goto.77nn.it
2024-12-05

Today I'm really pissed off.

The website of my #remote #desktop management application of choice has been blocked by our corporate's policies, therefore I can't download any more updates for it...

So this application is unsafer by a tiny bit every day new versions are not installed and I cannot guarantee, under my responsibility, that it is being stewarded (...updated, assessed...) correctly. So I can only remove it from my system.

Why don't I use a single RDP server and access all the others via console? Yes I do it for most of the job, but sometimes you've got to see what it feels like, you need to launch installers, applications and graphical tools that all the #Powershell of the world can't give you a feedback about.

Why don't I use #RDM by #Sysinternals? Because I can't do it properly, as some specific settings on our environment makes it unusable. Well, I could use it if I really wanted to script the remote servers creation phase, injecting the extra settings needed by the .rdp files, but...

Fuck you! I refuse

I will not do this. I will just keep a folder where I'll add a new .rdp file, manually crafted, every time I need to access one of my more than 700 supported Windows servers. It will take an insane amount of time, but this is how my company wants to spend their money, otherwise they would have provided me with the same capability they brought me away.

I was so pissed off that without realizing I built my menu-based RDM app from ground up in Powershell, and I'm going to share it on #Codeberg in the next days.

* List servers in a .csv file with some properties
* Pattern-search or filter the list by properties
* Connect to a server via mstsc
* Generate the .rdp for a server
* Add (or update) a server to the list
* Remove a server from the list
* Keeps track of last connection timestamp and connection count for each server
Select command: (<C>onnect, <G>enerate .rdp, <L>ist, <A>dd, <R>emove, e<X>it)?

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst