Message Box Interception, auto-answer "System Settings Change" popup.

[psucro]

I've used the standard XPE, message box interception application to try
to auto-answer the "new device detected" popup.

This popup has a title of "System Settings Change", and says press OK
to reboot for new settings to take effect.

I notice on this dialog, the "X" for cancel is blanked out.

I try to issue a WM_CLOSE to this window, when found, but it does not
go away.

I've also try to simulate the keystrokes of pressing cancel.
(This results in TAB to goto the next button, then SPACE or RETURN
to acknowledge the pushbutton.)

Note: I used the standard application from microsoft for "Message Box
Interception", which will ID all windows on the desktop, then cause a
WM_CANCEL to occur on the window you want to destroy.
(This appears to work great for other windows, but not this one.)

Neither method works.

I have an application where users will plug in USB memory device.
Not all devices are recognized, but I have not found one, which does
not work.
---> Many devices cause the new device detected to occur.

I've seen methods of auto-response for these message, but for this
popup, this would result in the system forever rebooting.

I've also seen the option of disabling the device wizard, but this has
the side effect that if I want to add a device, I need to rename some
exe's and dll's.

I would like to just have a service/application which will auto-respond
to this "System Settings Change" popup, and press cancel.

Any ideas, would be appreciated.

 

[KM]

There is a few sources where that message box is coming from.
I'd think that yours is coming from cmprops.dll.

Do you have "WMI Management Snapins" component in your configuration? If you do, remove it.
Or, better, just for testing purposes... From your working runtime remove *cmprops.dll* library from windows\system32 folder and
test connecting devices.
But be aware that without the library you will lose some [all] GUI for WMI service configurations.

--
Regards,
KM, BSquare Corp.

PS. There should be another message box with MB_YESNO style before the MB_OK. So I am confused why you only saw the dialog with OK
button.
Did you already happen to setup the auto-answer in message box interception application? I am wondering if "Yes" gets auto-selected.

 

[Guest]

psucro,
what is the standard application for message box interception that you used?
I searched MSDN for "Message Box Interception", and found a sample service
that polls for messageboxes and allows you to close them. Is that it (Is
there a name for this app)? I had this problem a while ago, and didn't want
to get rid of all message boxes (there is a way you can do this through the
registry), so I just did a periodic findwindow(NULL, "System Settings
Change") and then hide the window.