Utilities have exception under Windows Server 2019/2022

[Zeroes1]

General description of bug:

both fastfetch.exe and flashfetch.exe have exception c0000005 under Windows Server 2019/2022

• What happened:
• run fastfetch.exe process show info

                                      s.dindikov@sapsrv1
  /////////////////  /////////////////    -------------------
  /////////////////  /////////////////    OS: Windows Server 2022 (Datacenter) x86_64
  /////////////////  /////////////////    Host: VMware7,1
  /////////////////  /////////////////    Kernel: 10.0.20348.1787 (21H2)
  /////////////////  /////////////////    Uptime: 15 days, 18 hours, 49 mins
  /////////////////  /////////////////    Shell: Far
  /////////////////  /////////////////    Display: 1676x936 @ 32Hz
  /////////////////  /////////////////    DE: Fluent
                                      WM: Desktop Window Manager
  /////////////////  /////////////////    WM Theme: Aero - #0078D7 (System: Dark, Apps: Light)
  /////////////////  /////////////////    Font: Segoe UI (12pt) [Caption / Menu / Message / Status]
  /////////////////  /////////////////    Cursor: По умолчанию (32px)
  /////////////////  /////////////////    Terminal: Console Window Host 10.0.20348.1787
  /////////////////  /////////////////    Terminal Font: Consolas (20pt)
  /////////////////  /////////////////    CPU: Intel(R) Xeon(R) E5-2660 v3 (2) @ 2,6 GHz

  after proccess is ended (but no exit to shell) need press ctrl-c

run flashfetch.exe and nothing.... need press ctrl-c to show info after this auto exit to console

• What should happen:

• normal work, show info and exit proccess

• Where did you get the binary: Github Release

• Does this issue still occurs in the latest dev build? YES

Often helpful information:

trouble 100% reproduced

Output of fastfetch --version:

fastfetch 1.11.3 (x86_64)

[Zeroes1]

DMP+WER INFO bug.zip

[CarterLi]

Does registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\ exist? If yes, please paste the screenshot of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{*}\0000 here. Like this

[Zeroes1]

[Zeroes1]

both 2019 and 2022 servers are virtual based VMware vSphere

[CarterLi]

I don't see much difference from mine

I can't do much without getting a stack trace. I have added some debug log in the latest dev build. Please try it with fastfetch -s gpu --pipe

[Zeroes1]

1) run fastfetch.exe or flashfetch.exe from (CMake (Windows): remove an unused dependency #1346) build crashed under 2019/2022

2) now run fastfetch.exe or flashfetch.exe without any options from (GPU (Windows): add debug logs for #484 #1348) build work fine! not crashed under 2019/2022

3) D:\install\dindikov\test>fastfetch -s gpu --pipe ffPrintGPU start ffDetectGPU start ffDetectGPUImpl: start ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl EnumDisplayDevicesW ffDetectGPUImpl deviceKeyLength 0 ffDetectGPUImpl end ffDetectGPU end 1 ffPrintGPU 1 ffPrintGPU 2 ffPrintGPU 3 ffPrintGPU 4

[CarterLi]

ffDetectGPUImpl deviceKeyLength 0

That's not expected. Anyway, I have pushed a work around for this. Please test the latest dev build

[Zeroes1]

Under 2019/2022 work fine, thanks! May be to release 1.14?