Hello, I have a question regarding a custom EXE/script sensor. I wrote a powershell script, which checks if a previously defined network drive is mapped or not. If the drive is mapped, the script returns "0:drive is connected". If the drive is not mapped or the connection is not present, the script returns "2:connection interrupted". I created the sensor, pointed to my script, saved it and chose prtg.standardlookup.aws.statevalue for my valuelookup. The sensor returns the correct value ONLY for local drives. As soon as I map a network drive and edit my script to check for the newly created drive, the sensor gets the input "2:connection interrupted", even tho the drive is mapped correctly. If I run the script by itself at that monent it returns "0:drive is connected". Only in combination with PRTG/the sensor, the script puts out a wrong message. I even installed a remote probe to test it there on a different computer. But for some reason it will not work for network drives. How can I fix this issue? If you need more information, please let me know.