VS 14.0.25431.01 Update 3
Windows 10 - 10.0.10240 Build 10240
Steps:
- Create a new MFC application.
- Add
ASSERT( 0 ) to CAboutDlg::CAboutDlg , for example. - Create a debug version.
- Run without debugging ( Ctrl + F5 ).
- Click "About" → "Silent" ABORTED
- Start debugging ( F5 )
- Click "About" → Breakpoint Dialog Box .
Microsoft closed the error as “by design”: “Based on a review of the information provided, we resolved this problem as“ by design. "We cannot identify anything here, which is unexpected behavior."
Works great with Win7.
I am looking for a workaround.
[EDIT] I found that __acrt_get_developer_information_policy() returns developer_information_policy_none instead of the expected developer_information_policy_ui (see common_show_message_box in crtmbox.cpp ), but I don’t know how to change it.
[EDIT] See link and one at Microsoft Connect.
[EDIT] The latest Windows 10 SDK fixed the problem on my machines. All credits go to cubee_72 (MS account).
[EDIT] The latest version of the SDK only resolved the issue for Ctrl + F5 . If a debugger is present, the breakpoint dialog is still displayed, not the confirmation dialog.
[EDIT 2017-11-20] MS has deleted my error reports.
Thanks.
source share