UVK forums

Could it be that you were using an earlier SFX package on the two PCs where it happened, but can't recreate the issue with a new SFX package?

Xander, I haven't run into this issue. Did you uninstall and remove any remnants from previous versions?

Thank you Fred. It's working well now. This will make it easier to deploy UVK remotely.

Still not resolved in v. 10.4.0.0. Will you fix this for the next update? And could you add an option to create a branded version of the SFX archive, perhaps with some auto-delete function so that customers won't be able to run it? Thanks.

Still getting two shortcuts on the desktop. And the tooltip shows the company name in duplicate.

Thanks Fred.

When running the SFX archive UVKPortable.exe, two shortcuts will appear on the desktop, the branded and the UVK shortcut.

The problem with these machines, and I'm starting to believe they are all HP, is that they have no BaseBoard with 0Ah at offset 13, so Motherborad info is retrieved through WMI. I would surely like to know how many baseboard tables they have, and what is the value of the BYTE at offset 13.

This ...

Yes, and in the case of XP there are few copies of XP Pro x64 because of the compatibility problems with 16-bit and some 32-bit software and MS-DOS.

That's a possibility. Another reason might be that the error occurs in UVK_en64.exe; but it never runs in Windows 7 or XP because they are 32-bit (which I should have mentioned earlier).

Thank you for identifying and solving the problem so quickly. The affected machine was an HP a1640n desktop PC. Here's a summary of the BIOS:

SMBIOS 2.4 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Phoenix Technologies, LTD
Version: 3.15
Release Date: 02/05/2007 ...

Problem solved! System Info is now working and no longer crashes. Here is the content of the latest UVK_debug:

Debug break point 1
Debug break point 2
Debug break point 9
Debug break point 10
Debug break point 11
Debug break point 11
Debug break point 11
Debug break point 11

What caused this error ...

I don't mind at all
The next UVK_debug contains:

Debug break point 1
Debug break point 2

Sounds like you're getting closer to solving it. The next UVK_debug contains:

Debug break point 1
Debug break point 2
Debug break point 3
Debug break point 10
Debug break point 11
Debug break point 12
Debug break point 14
Debug break point 16

Thanks Fred. Here's the content of the next UVK_debug:

Debug break point 1
Debug break point 2
Debug break point 3

You're probably right, Charger440. It's early in the debugging process, and Fred could set up additional breakpoints to track down the source of the error.

Glad to help
Yes it's 64-bit. I extracted both files and ran UVK_en.exe. UVK_debug appeared on the desktop, and it contains:

Debug break point 1

I also ran an earlier version of UVKPortable, v.7.7.2.0, on the same Windows 10 machine and it did not crash when running System Info.

Hi Fred,
I ran the extracted UVK_en.exe from the UVK directory and it crashed again as you predicted. But the file UVK_debug.txt was not created on the desktop or any other folder.

When selecting System Info from the Home menu in v.9.6.0.0, Windows will terminate UVK with an error message. This only seems to occur in Windows 10. No problem running System Info in Windows 7 or XP.