How to programmatically force use of the old print dialog in Windows 11 22H2

Helg Green 5

Please tell me how to programmatically force the use of the old print dialog in Windows 11 22H2 in C ++? For example, using the PrintDlgEx() and PrintDlg() functions also invokes a new print dialog instead of the old one. There is also a way to make an entry in the registry, but it is not suitable, because if the application crashes, it will not be possible to change the value back in the registry.

The problem with the new dialog is that it is incorrectly initialized: if the initial mode "print range" is selected, instead of the range for example "1-2" it is displayed simply "1-" without the last digit.

Note:

Using GetForegroundWindow() to get another application's window does not reproduce the issue. The window must be created by your application, then the print dialog will always be displayed in the new style. The problem only affects Windows 11 22H2, in earlier versions the print dialog is used in the old style.

Minxin Yu 11,506 Reputation points Microsoft Vendor

2023-07-17T06:32:38.8633333+00:00

What kind of C++ project are you using? Can you provide a minimal reproducible example?
Castorix31 84,546 Reputation points

2023-07-17T14:45:38.28+00:00

I don't have Windows 11, but you could build your own simplified PrintDlg DialogBox (ComboBox for printers, Edit controls for pages, msctls_updown32 for copies, ...)
David Lowndes 2,535 Reputation points MVP

2023-07-17T16:58:57.43+00:00

Do you have a minimal example project (or small code example that can be pasted) that reproduces the problem?

Helg Green 5

#include <windows.h>
#include <commdlg.h>
#include <QWidget>
#include <QApplication>

#define MAXPAGERANGES 32


int main(int argc, char *argv[])
{
    QApplication app(argc, argv);
    QWidget w;
    w.show();

    HWND hwnd = (HWND)w.winId();

    const DWORD toPage = 100;

    PRINTPAGERANGE *page_ranges = new PRINTPAGERANGE[MAXPAGERANGES];
    memset(page_ranges, 0, sizeof(PRINTPAGERANGE) * MAXPAGERANGES);
    page_ranges[0] = {1, toPage};

    PRINTDLGEX dlg;
    ZeroMemory(&dlg, sizeof(dlg));
    dlg.lStructSize    = sizeof(dlg);
    dlg.Flags          = PD_PAGENUMS;
    dlg.hInstance      = NULL;
    dlg.hwndOwner      = hwnd;
    dlg.nStartPage     = START_PAGE_GENERAL;
    dlg.nCopies        = 1;
    dlg.nMaxPageRanges = MAXPAGERANGES;
    dlg.nPageRanges    = 1;
    dlg.lpPageRanges   = page_ranges;
    dlg.nMinPage       = 1;
    dlg.nMaxPage       = toPage;

    if (PrintDlgEx(&dlg) == S_OK) {
        switch (dlg.dwResultAction) {
        case PD_RESULT_PRINT: {
            LPDEVMODE pDevmode = (LPDEVMODE)GlobalLock(dlg.hDevMode);
            if (pDevmode) {
                LPWSTR localPrinterName = NULL;
                localPrinterName = pDevmode->dmDeviceName;
                wprintf(L"%s\n", localPrinterName);
            }
            GlobalUnlock(dlg.hDevMode);
            break;
        }
        default:
            break;
        }
        if (dlg.hDevMode)
            GlobalFree(dlg.hDevMode);
        if (dlg.hDevNames)
            GlobalFree(dlg.hDevNames);
//        if (dlg.hDC)
//            DeleteDC(dlg.hDC);
    }
    delete[] page_ranges;

    return app.exec();
}

David Lowndes 2,535 MVP

I'm afraid I can't reproduce your issue.
Using the following code (not a good example, so no-one copy it) in an x64 console project:

#include <Windows.h>

int main() { PRINTDLGEX pdx{ .lStructSize{sizeof( pdx )} };

// Allocate an array of PRINTPAGERANGE structures.
LPPRINTPAGERANGE pPageRanges = (LPPRINTPAGERANGE) GlobalAlloc( GPTR, 10 * sizeof( PRINTPAGERANGE ) );
if ( !pPageRanges )
    return E_OUTOFMEMORY;

pPageRanges->nFromPage = 2;
pPageRanges->nToPage = 100;

pdx.hwndOwner = GetForegroundWindow();
pdx.Flags = PD_PAGENUMS;
pdx.nPageRanges = 1;
pdx.nMaxPageRanges = 10;
pdx.lpPageRanges = pPageRanges;
pdx.nMinPage = 1;
pdx.nMaxPage = 100;
pdx.nCopies = 1;
pdx.nStartPage = START_PAGE_GENERAL;

auto hResult = PrintDlgEx( &pdx );
}

On Win10-22H2, Win11-21H2, and Win11-22H2, I see the same dialog with the page range showing OK:

enter image description here

Helg Green 5 Reputation points

2023-07-18T05:47:41.71+00:00

I forgot to clarify that if you use GetForegroundWindow() to get the window of another application, then the problem is not reproduced. The window must be created by your application, then the print dialog will always appear in the new style. It is not clear why using a window from another application has such an effect.
The problem only applies to Windows 11 22H2, in earlier versions the print dialog is used in the old style.
(Added a note)

Minxin Yu 11,506 Microsoft Vendor

Quick test in MFC dialog app. And it gave me 2-100. Will the problem occur in your MFC dialog instead of QT?

User's image

void CMFCApplication1Dlg::OnBnClickedButton1()
{
	PRINTDLGEX pdx{ .lStructSize{sizeof(pdx)} };

	// Allocate an array of PRINTPAGERANGE structures.
	LPPRINTPAGERANGE pPageRanges = (LPPRINTPAGERANGE)GlobalAlloc(GPTR, 10 * sizeof(PRINTPAGERANGE));
	if (!pPageRanges)
		return ;

	pPageRanges->nFromPage = 2;
	pPageRanges->nToPage = 100;

	pdx.hwndOwner = m_hWnd;
	pdx.Flags = PD_PAGENUMS;
	pdx.nPageRanges = 1;
	pdx.nMaxPageRanges = 10;
	pdx.lpPageRanges = pPageRanges;
	pdx.nMinPage = 1;
	pdx.nMaxPage = 100;
	pdx.nCopies = 1;
	pdx.nStartPage = START_PAGE_GENERAL;

	auto hResult = PrintDlgEx(&pdx);// TODO: Add your control notification handler code here
}

Helg Green 5 Reputation points

2023-07-18T07:59:54.49+00:00

I tried to create a window using WinApi CreateWindowEx() the problem is also repeated.
Minxin Yu 11,506 Reputation points Microsoft Vendor

2023-07-18T08:07:18.8333333+00:00

Can you provide an example?

Helg Green 5

LRESULT WndProc(HWND hWnd, UINT msg, WPARAM wParam, LPARAM lParam)
{
    switch (msg) {
    case WM_NCCALCSIZE: {
        if (wParam == TRUE) {
            SetWindowLong(hWnd, DWLP_MSGRESULT, 0);
            return TRUE;
        }
        return FALSE;
    }
    case WM_PAINT:
        return 0;

    default:
        break;
    }
    return DefWindowProc(hWnd, msg, wParam, lParam);
}


HINSTANCE hInstance = GetModuleHandle(NULL);
WNDCLASSEX wcx{sizeof(WNDCLASSEX)};
wcx.style = CS_HREDRAW | CS_VREDRAW;
wcx.hInstance = hInstance;
wcx.lpfnWndProc = WndProc;
wcx.cbClsExtra	= 0;
wcx.cbWndExtra	= 0;
wcx.lpszClassName = L"MyWindow";
wcx.hbrBackground = (HBRUSH)(COLOR_WINDOW + 1);
wcx.hCursor = LoadCursor(hInstance, IDC_ARROW);
RegisterClassEx(&wcx);

HWND hwnd = CreateWindowEx(
            WS_EX_OVERLAPPEDWINDOW,
            L"MyWindow",
            L"MainWindow",
            WS_MAXIMIZEBOX | WS_THICKFRAME,
            100, 100, 500, 400,
            NULL,
            NULL,
            hInstance,
            NULL);

ShowWindow(hwnd, SW_SHOW);

Minxin Yu 11,506 Microsoft Vendor

I cannot reproduce your problem.

User's image

#include <Windows.h>


LRESULT WndProc(HWND hWnd, UINT msg, WPARAM wParam, LPARAM lParam)
{
	switch (msg) {
	case WM_CREATE:
		CreateWindowA("BUTTON", "Click here", WS_VISIBLE | WS_CHILD | BS_PUSHBUTTON,
			10, 10, 200, 30, hWnd, (HMENU)1, NULL, NULL);
		break;
	case WM_NCCALCSIZE: {
		if (wParam == TRUE) {
			SetWindowLong(hWnd, DWLP_MSGRESULT, 0);
			return TRUE;
		}
		return FALSE;
	}
	case WM_COMMAND:
	{
		int wmId = LOWORD(wParam);
		switch (wmId)
		{
		case 1:
		{

			PRINTDLGEX pdx{ .lStructSize{sizeof(pdx)} };

			// Allocate an array of PRINTPAGERANGE structures.
			LPPRINTPAGERANGE pPageRanges = (LPPRINTPAGERANGE)GlobalAlloc(GPTR, 10 * sizeof(PRINTPAGERANGE));
			if (!pPageRanges)
				return E_OUTOFMEMORY;

			pPageRanges->nFromPage = 2;
			pPageRanges->nToPage = 100;

			pdx.hwndOwner = hWnd;
			pdx.Flags = PD_PAGENUMS;
			pdx.nPageRanges = 1;
			pdx.nMaxPageRanges = 10;
			pdx.lpPageRanges = pPageRanges;
			pdx.nMinPage = 1;
			pdx.nMaxPage = 100;
			pdx.nCopies = 1;
			pdx.nStartPage = START_PAGE_GENERAL;

			auto hResult = PrintDlgEx(&pdx);
		}
		break;
		default:
			return DefWindowProc(hWnd, msg, wParam, lParam);
		}
	}

	case WM_PAINT:
		return 0;

	default:
		break;
	}
	return DefWindowProc(hWnd, msg, wParam, lParam);
}


int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow)
{

	hInstance = GetModuleHandle(NULL);
	WNDCLASSEX wcx{ sizeof(WNDCLASSEX) };
	wcx.style = CS_HREDRAW | CS_VREDRAW;
	wcx.hInstance = hInstance;
	wcx.lpfnWndProc = WndProc;
	wcx.cbClsExtra = 0;
	wcx.cbWndExtra = 0;
	wcx.lpszClassName = L"MyWindow";
	wcx.hbrBackground = (HBRUSH)(COLOR_WINDOW + 1);
	wcx.hCursor = LoadCursor(hInstance, IDC_ARROW);
	RegisterClassEx(&wcx);

	HWND hwnd = CreateWindowEx(
		WS_EX_OVERLAPPEDWINDOW,
		L"MyWindow",
		L"MainWindow",
		WS_MAXIMIZEBOX | WS_THICKFRAME,
		100, 100, 500, 400,
		NULL,
		NULL,
		hInstance,
		NULL);

	ShowWindow(hwnd, SW_SHOW);
	UpdateWindow(hwnd);

	MSG msg;
	while (GetMessage(&msg, NULL, 0, 0))
	{
		TranslateMessage(&msg);
		DispatchMessage(&msg);
	}

	return (int)msg.wParam;
}

Helg Green 5 Reputation points

2023-07-18T09:22:36.3566667+00:00

Are you sure you're using Windows 11 22H2? Judging by the fact that the corners of the window are not rounded, I think not.
Minxin Yu 11,506 Reputation points Microsoft Vendor

2023-07-18T09:25:11.0766667+00:00

Yes.
Helg Green 5 Reputation points

2023-07-18T09:28:36.0733333+00:00

Do you get a new print dialog in other applications? perhaps you have an old dialog appearing in all applications? This usually happens when the "HKEY_CURRENT_USER\Software\Microsoft\Print\UnifiedPrintDialog" registry value "PreferLegacyPrintDialog" is set to 1.
Minxin Yu 11,506 Reputation points Microsoft Vendor

2023-07-18T09:45:41.9133333+00:00

This is visual style in MFC. I checked the registry. It is none.
David Lowndes 2,535 Reputation points MVP

2023-07-18T11:13:07.1466667+00:00

I've now tried the code in a Win32 desktop program, and I also don't have that registry setting on Win11 22H2, and I still see the dialog shown above in the test program and all other programs (such as Notepad) that I've tried.
Can you show a screen shot of the problematic dialog that you see please?

I wonder if there's some difference between viewing on the console and a remote desktop connection - as the only Win11 machines I have are VMs connected through remote desktop?
Helg Green 5 Reputation points

2023-07-18T11:57:22.34+00:00

Is there an easy way to apply visual styles without using MFC, using only WinApi?
David Lowndes 2,535 Reputation points MVP

2023-07-18T13:16:17.18+00:00

OK, can you try using a remote desktop connection to that machine to see if you then see the old dialog (as I do)?
Helg Green 5 Reputation points

2023-07-18T17:11:00.1933333+00:00

Unfortunately, I do not have a second computer to do this, I have Windows 11 installed as the main system.
Helg Green 5 Reputation points

2023-07-18T20:18:35.4233333+00:00

Without the use of MFC, it is not realistic to call the old dialog, did I understand correctly?
David Lowndes 2,535 Reputation points MVP

2023-07-18T20:22:21.7166667+00:00

@Helg Green I suspect the use of MFC is irrelevant. Perhaps others are also testing Win11 22H2 on VMs with remote desktop as I am - since my PC doesn't meet the Win11 hardware requirements.
Helg Green 5 Reputation points

2023-07-18T21:22:07.8533333+00:00

I checked using the MFC, the old dialog is indeed displayed there, but how to do this without the MFC is not yet clear.
David Lowndes 2,535 Reputation points MVP

2023-07-18T21:32:16.6333333+00:00

Shooting from the hip here then.
Does your real application have a V6 common control manifest, and your MFC test project not?
Helg Green 5 Reputation points

2023-07-19T06:06:15.73+00:00

I added the manifest, called InitCommonControls(), but it had no effect.
Minxin Yu 11,506 Reputation points Microsoft Vendor

2023-07-19T08:48:26.27+00:00

I reproduced your problem. You could report the bug to Developer Community and post link here.

Best regards,
Helg Green 5 Reputation points

2023-07-19T09:06:19.4666667+00:00

The fact that this is a bug in the new print dialog was already clear, I just need a way to get around this bug by switching to the old dialog (without using MFC).
David Lowndes 2,535 Reputation points MVP

2023-07-19T11:27:06.76+00:00

@Helg Green I was wondering whether your application already had a manifest - so removing it might (or might not) have some bearing.
Also, it is worthwhile reporting the issue and posting a link back here so that we can vote it up. Hopefully someone will be able to pass it onto the Windows team responsible. If you have a customer with some weight behind them, it wouldn't hurt for them to report it to MS too :)
Minxin Yu 11,506 Reputation points Microsoft Vendor

2023-07-20T01:52:23.47+00:00

I checked using the MFC, the old dialog is indeed displayed there, but how to do this without the MFC is not yet clear.

On another test machine of mine, MFC does not display the old dialog. It may depend on your operating system.
David Lowndes 2,535 Reputation points MVP

2023-07-30T10:53:37.03+00:00

To satisfy my curiosity I've installed the latest Win11 (thanks to Rufus for taking the pain out of installing it on unsupported hardware) and can confirm that it does reproduce this problem both locally and when viewed via remote desktop. I conclude that it's only when Win11 is installed on a VM that we don't get the new (flawed) print dialog. Unfortunately, a VM installation is a staple thing for developer testing.
What a tangled web we weave!

2 answers

Dave Milner 5 Reputation points

2024-09-16T21:37:15.96+00:00

Helg,

I know it's a little late for you, but I recently had to correct the same problem. The "modern" print dialog has the big empty No Preview Available space that looks like the user is missing something.

To get the older print dialog I used the PrintDlg function (instead of PrintDlgEx) that uses the PRINTDLG structure and not the PRINTDLGEX structure. I added the PD_ENABLEPRINTHOOK flag to the flags and created a dummy print hook function:

UINT_PTR __stdcall DummyPrintHookProc (HWND unnamedParam1, UINT unnamedParam2, WPARAM unnamedParam3, LPARAM unnamedParam4) { return 0; }

and put .lpfnPrintHook = &DummyPrintHookProc; to make sure the function is noticed.

Adding the printer hook procedure prevented windows from using the new dialog, but just for that call. It did not change the settings for any other programs or any other call of the print dialog.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
MCB 0 Reputation points

2023-07-17T16:05:18.5533333+00:00

I have the same question
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to programmatically force use of the old print dialog in Windows 11 22H2

2 answers

Your answer