Windows 11 VPE compatibility & Print dialog (Clarification)

[Brent Rose]

Would it be possible to have some definitive summary to clarify "where things are at" with respect to Windows 11 please. Basically, I want to move a development PC to Windows 11 for some older applications using VPE 7.20, and want to make sure this is not going to bite me (like having applications freeze)!

a) Is VPE 7.2 compatible with Windows 11, or are there issues requiring upgrade to the latest version?

Regarding the issues with the Windows 11 print dialogue:

b) Has the VPE engineered custom print dialogue proven to address all known issues (I would imagine so!!), or are there still potential problems courtesy of MS?

c) Is the VPE print dialogue only available via upgrade to the latest version (from 7.20)?

If I'm still having to use VPE 7.2 (and potentially having print issues):

d) Has a call to CoInitializeEx(NULL, COINIT_APARTMENTTHREADED) and CoUninitialize() as mentioned in this forum proven to at least resolve "some" issues (viz are there significant issues it does NOT resolve)?

I see elsewhere that the older print dialogue can potentially be restored via a registry setting:

reg add "HKCU\Software\Microsoft\Print\UnifiedPrintDialog" /v "PreferLegacyPrintDialog" /d 1 /t REG_DWORD /f

e) Has this been tried (successfully) as a stop-gap solution? Using a deprecated dialogue is obviously a nasty solution, but might be a short term bail out.

Thanks.

[IDEAL Software Support]

a) Is VPE 7.2 compatible with Windows 11, or are there issues requiring upgrade to the latest version?

The only issue is the buggy print dialog of Win 11.

b) Has the VPE engineered custom print dialogue proven to address all known issues (I would imagine so!!), or are there still potential problems courtesy of MS?

Yes.

c) Is the VPE print dialogue only available via upgrade to the latest version (from 7.20)?

Yes.

d) Has a call to CoInitializeE

It fixes the problem with freezing your application. It does not fix the problem with unusable SetupPrinter() calls using PRS files, nor that the dialog remembers a specified printing device.

HKCU\Software\Microsoft\Print\UnifiedPrintDialog

There was some problem with it, but I don't remember the details. Maybe Windows Update did reset the setting or something like this.