From f57a8340437e843d810499fa40c00c302db9d939 Mon Sep 17 00:00:00 2001 From: 0xdefec71f <35151132+0xdefec71f@users.noreply.github.com> Date: Sun, 1 Nov 2026 19:08:47 +0100 Subject: [PATCH] Fix hardcoded user path in silent VBS launcher Replace the hardcoded user-specific PowerShell script path with dynamic path resolution. Previously, the launcher used a hardcoded path containing "C:\Users\User", which caused it to fail for users with a different Windows username. The VBS launcher now determines its own directory using WScript.ScriptFullName and starts DimOLED.ps1 from the same directory. This ensures the launcher works correctly for all Windows users and installation paths without requiring any user-specific configuration or modifications during installation. --- DimOLED_Silent.vbs | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/DimOLED_Silent.vbs b/DimOLED_Silent.vbs index 6271785..4d48168 100644 --- a/DimOLED_Silent.vbs +++ b/DimOLED_Silent.vbs @@ -1,2 +1,3 @@ Set WshShell = CreateObject("WScript.Shell") -WshShell.Run "powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -File ""C:\Users\User\AppData\Local\DimOLED\DimOLED.ps1"" -Silent", 0, False +ScriptDir = CreateObject("Scripting.FileSystemObject").GetParentFolderName(WScript.ScriptFullName) +WshShell.Run "powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -File """ & ScriptDir & "\DimOLED.ps1"" -Silent", 0, False