Describe the bug
When installing Angry IP Scanner version 3.10.0 on Windows (confirmed on Windows 11 x64), the application produces an error notification after scanning:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
no swt-gdip-win32-4973r2 in java.library.path: C:\Program Files\Angry IP Scanner\jre\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS; ...
no swt-gdip-win32 in java.library.path: ...
no swt-gdip in java.library.path: ...
Can't load library: C:\Users<Username>.swt\lib\win32\x86_64\swt-gdip-win32-4973r2.dll
Can't load library: C:\Users<Username>.swt\lib\win32\x86_64\swt-gdip-win32.dll
Can't load library: C:\Users<Username>.swt\lib\win32\x86_64\swt-gdip.dll
)
The underlying cause is an UnsatisfiedLinkError looking for a specific version of the GDI+ library (swt-gdip-win32-4973r2).
Upon examining the populated library extraction directory (C:\Users<Username>.swt\lib\win32\x86_64), the file swt-gdip-win32-4973r2.dll is completely missing. Instead, the folder only contains updated r12 variants (swt-win32-4973r12.dll and swt-osversion-win32-4973r12.dll).
Manually copying and renaming the existing r12 file to match the expected r2 name tricks the app into executing, but immediately results in a deeper structural crash:
java.lang.UnsatisfiedLinkError: 'int org.eclipse.swt.internal.gdip.Gdip.GdiplusStartupinput_sizeof 0'.
Downgrading to version 3.9.3 completely resolves the issue, confirming a regression or library packaging mismatch in the 3.10.0 release.
To Reproduce
- Clean install Angry IP Scanner 3.10.0 using the standard Windows installer.
- Attempt to launch the application.
- Observe the crash window displaying the UnsatisfiedLinkError
Expected behavior
Expected program to run and not produce an error notification
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please copy from the About dialog or complete manually):
- Version of Angry IP Scanner: 3.10.0
- OS, version, CPU architecture: Windows 11, 25H2, x64
- Windows installer was used with bundled Java
- Last working version of Angry IP Scanner: 3.9.3
Describe the bug
When installing Angry IP Scanner version 3.10.0 on Windows (confirmed on Windows 11 x64), the application produces an error notification after scanning:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
no swt-gdip-win32-4973r2 in java.library.path: C:\Program Files\Angry IP Scanner\jre\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS; ...
no swt-gdip-win32 in java.library.path: ...
no swt-gdip in java.library.path: ...
Can't load library: C:\Users<Username>.swt\lib\win32\x86_64\swt-gdip-win32-4973r2.dll
Can't load library: C:\Users<Username>.swt\lib\win32\x86_64\swt-gdip-win32.dll
Can't load library: C:\Users<Username>.swt\lib\win32\x86_64\swt-gdip.dll
)
The underlying cause is an UnsatisfiedLinkError looking for a specific version of the GDI+ library (swt-gdip-win32-4973r2).
Upon examining the populated library extraction directory (C:\Users<Username>.swt\lib\win32\x86_64), the file swt-gdip-win32-4973r2.dll is completely missing. Instead, the folder only contains updated r12 variants (swt-win32-4973r12.dll and swt-osversion-win32-4973r12.dll).
Manually copying and renaming the existing r12 file to match the expected r2 name tricks the app into executing, but immediately results in a deeper structural crash:
java.lang.UnsatisfiedLinkError: 'int org.eclipse.swt.internal.gdip.Gdip.GdiplusStartupinput_sizeof 0'.
Downgrading to version 3.9.3 completely resolves the issue, confirming a regression or library packaging mismatch in the 3.10.0 release.
To Reproduce
Expected behavior
Expected program to run and not produce an error notification
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please copy from the About dialog or complete manually):