Closed Hellzbellz123 closed 6 years ago
@Wagnard
Commit - 543ebac - 24 Jun
Particular reason for this change... ? Its what causing this issue.
@display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb:Line 131
-: m_exefile = Assembly.GetExecutingAssembly().Location
+: m_exefile = New Uri(Assembly.GetExecutingAssembly().CodeBase).LocalPath
Uri trims out path after char '#' (found at 'Uri.Fragment') and escapes special chars. '#' is valid char in windows file path, including '(){}[]&@%,+'
Users path
Incorrectly escaped into
and set to m_exefile (Application.Paths.AppExeFile)
.. Because user didn't launch DDU as Admin rights, DDU attempts launch itself as admin using incorrect path "C:\Users\Other peeps\Downloads\" (Application.Paths.AppExeFile) => which is a folder and Windows doesn't know how to execute folder...
Because exe path is invalid, most of other paths are as well... (Settings, DDU Logs, Languages)
I can confirm what you are saying. The change was done while testing for a user having issues to start DDU, it seems I forgot to revert this as it was not what fix it for him. Thanks for the info ;)
Le mar. 14 août 2018 à 16:32, devmltk notifications@github.com a écrit :
@Wagnard https://github.com/Wagnard
*Commit - 543ebac https://github.com/Wagnard/display-drivers-uninstaller/commit/543ebac9ca38ec624e7ad01ff703030b40fbf328
- 24 Jun*
Particular reason for this change... ? Its what causing this issue.
@display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb:Line 131
-: m_exefile = Assembly.GetExecutingAssembly().Location +: m_exefile = New Uri(Assembly.GetExecutingAssembly().CodeBase).LocalPath
Uri trims out path after char '#' (found at 'Uri.Fragment') and escapes special chars. '#' is valid char in windows file path, including '(){}[]&@%,+'
Users path
- 'C:\Users\Other peeps\Downloads##\DDU v17.0.9.1\Display Driver Uninstaller.exe'
Incorrectly escaped into
- 'C:\Users\Other peeps\Downloads\'
and set to m_exefile (Application.Paths.AppExeFile)
.. Because user didn't launch DDU as Admin rights, DDU attempts launch itself as admin using incorrect path "C:\Users\Other peeps\Downloads\" (Application.Paths.AppExeFile) => which is a folder and Windows doesn't know how to execute folder...
- ERROR_NO_ASSOCIATION (0x483) <-- not 0x8483, my typo on code...
Because exe path is invalid, most of other paths are as well... (Settings, DDU Logs, Languages)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Wagnard/display-drivers-uninstaller/issues/42#issuecomment-413006231, or mute the thread https://github.com/notifications/unsubscribe-auth/AK9hmVyZUBW1a0Jm_3OpzlzXWGSZNt1nks5uQzPogaJpZM4VoIHv .
-- Ghislain Harvey Web administrator / Application Support Developer Microsoft Technology Associate (MTA) Email : wagnard28@gmail.com , info@wagnardsoft.com info@wagnardsoft.com Web : https://www.wagnardsoft.com http://www.wagnardsoft.com
I pushed the fix for the next version. @devmltk I do not see this typo in code 0x8483
Also fixed the error code to show the Uinteger value (1155)
Im getting an issue with all versions of DDU, it says unknown erroe (0x8483) and googling gave me no info