Re: How To Exit Explorer.exe Gracefully On Windows XP And Windows Vista 7

0 views

Skip to first unread message

Message has been deleted

Edel Dieringer

unread,

Jul 15, 2024, 10:44:49 PM7/15/24

to disdogsvete

Unfortunately, the method has two drawbacks; First, it uses an undocumented user message, which may change in future Windows versions, and second, it does not work under Windows XP, since the 'magic procedure' to exit windows is different (open the shutdown dialog, then cancel it pressing SHIFT-CTRL-ALT-ESC) and no message posting is involved there.

How to exit explorer.exe gracefully on Windows XP and Windows Vista 7

Download File ===> https://urlgoal.com/2yY3cn

It would be nice to have a reliable and portable way to terminate explorer cleanly from another process regardless of the windows version. So I continued debugging into the disassembly of the code which terminates explorer cleanly in order to find a hint about how I could achieve this. I still don't have the perfect solution but I made some interesting observations (on Windows 7 and Windows XP) which I want to share with whoever might be interested:

However, it bothers me that all my open windows of explorer will not be re-opened when the process is started again.Can the explorer be just suspended or gracefully closed so that the open explorer windows will remain?

No you can't. once you killed the process explorer.exe you can't retrieve every thing managed bye the explorer (windows-clipboards-...)The best to do is to use Windows Classic Theme and shutdown all processes that you don't need while playing e.g. download managers

WD, do you really think its acceptable to expect people to know enough to check in \windows\temp for these files, and remember to manually delete them? Do you really think its acceptable to expect people to write their own little batch file to manually terminate the WD software before shutting down windows?

Next you must specify the command line to execute, starting with the path to the hook script or executable. This could be a batch file, an executable file or any other file which has a valid windows file association, e.g. a perl script. Note that the script must not be specified using a UNC path as Windows shell execute will not allow such scripts to run due to security restrictions.

The default value is 0. With this setting, the icons are grouped together by application type. All dialogs from TortoiseSVN are grouped together, all windows from TortoiseMerge are grouped together, ...

If set to 1, then instead of all dialogs in one single group per application, they're grouped together by repository. For example, if you have a log dialog and a commit dialog open for repository A, and a check-for-modifications dialog and a log dialog for repository B, then there are two application icon groups shown in the Win7 taskbar, one group for each repository. But TortoiseMerge windows are not grouped together with TortoiseSVN dialogs.

If set to 2, then the grouping works as with the setting set to 1, except that TortoiseSVN, TortoiseMerge, TortoiseBlame, TortoiseIDiff and TortoiseUDiff windows are all grouped together. For example, if you have the commit dialog open and then double click on a modified file, the opened TortoiseMerge diff window will be put in the same icon group on the taskbar as the commit dialog icon.

This can be useful if you use something other than the windows explorer or if you get problems with the context menu displaying incorrectly. Set this value to false if you don't want TortoiseSVN to show icons for the shell context menu items. Set this value to true to show the icons again.

This Drive letter is a mapping to a network path, when people open the remote app and call explorer fonction, they see complete network patch into windows file explorer adsresse bar and not just the letter

Hi Carl
First thank you I use allot your site guides
Our organization moving for windows 10
we use folder redirection for appdata roaming for couple of reasons like IOPs and logon time.
After windows 10 Migration we noticed that the pinned taskbar icons are not saved after logoff \ reboot.
When we open the Appdata Roaming UNC path manually, we can see that the Pinned Icons are created successfully.

It has been a long time since I started working on automation shell windows, mainly Internet Explorer windows. There are times the WebBrowser control or the MFC class CHTMLView would satisfy my needs, but often I need to scratch my head, start embedding the WebBrowser control from scratch and then simulate as many IE behaviors as I can, such as implementing IDocHostUIHandler to enable AutoComplete in the WebBrowser control. A natural alternative is, well, why not just start automating an Internet Explorer window?

Then, what is the current instance of Internet Explorer? Well, it is the latest active IE window. Since Microsoft Windows will bring the active window to the top of the z-order, it will remain at the top of z-order among all IE windows. Therefore, what I have to do is to find out which IE window has the highest z-order value. So, I need to figure out first which window is an IE window. After some investigation using Spy++, I assume the window class name of the IE windows is "IEFrame", and I write a function to get the window class name of a shell window:

And the rest of this problem is simple: enumerate the top-level windows through the z-axis and find the first instance with the window class name "IEFrame" which is also in the shell window list. After that, I do something tricky to play with the IE DHTML Document Object Model (or DOM, which is available after the IE window fires the last DocumentComplete event) to ascertain that the window is attached successfully:

While examining the shell windows list of ShellWindows object, I get a by-product: it seems that the Windows Explorer windows also have a common window class name. Thus the same mechanism works for Windows Explorer windows with a slight change of window class name from "IEFrame" to "ExploreWClass". Since there is no DHTML DOM to play with, I tell the Windows Explorer window to browse an existing path, to flag that I have taken over this window.

Let's take our new achievement back to the old problem. Since I can attach to the current Windows Explorer window almost the same way as attaching to the current Internet Explorer window, can I create and automate a new Windows Explorer window similar to the way I create and automate a new Internet Explorer window? To my surprise, the answer is no. There is no class ID for Windows Explorer to create such a COM object. Although I can still create an IE window, navigate to a folder, and show the Folder Explorer Bar that makes it look like a Windows Explorer window, I can not change the window class name "IEFrame", thus distinguishing it from the other IE windows displaying HTML pages and Active Documents is difficult.

Wait, I have another object in my hand, the ShellWindows object. It can give me a list of shell windows, including every Windows Explorer windows and the corresponding IWebBrowser2 interface, a door to its IShellBrowser interface. Now I need to get two shell window lists, one before creating an explorer.exe process and one right after that; then I must compare them to find out the new shell window.

There is a large chunk of head-scratching code here. In addition, it takes some time getting used to the mixed COM and Windows API function calls. Hopefully, you would find this article useful, and not be confused with my code. Automating Internet Explorer and Windows Explorers windows can save you a lot of time, since you are able to avoid simulating the default behaviors of the system, and it provides a familiar look to the end users.

I have removed all Photoshop CS3 Beta manually (Use control panel, deleted files and registries) as instructed in this web and get rid of all thing involved Adobe out of my computer.When I clicked Setup.exe, a setup windows (See in appeared and then disappear!
Then nothing is happenned further. No error message. It just disappeared.I tried to run Windows in clean mode (msconfig -> disable unneccessary services) and also disable Antivirus and Firewall etc. But this problem persists.I'm running Windows Vista Home Premium (32Bit) and have Intel Centrino Duo 2.0GHz with 1.5GB of Ram (DDR2) and 100GB HDD. Graphic shared Intel 945GM Express Chipset.

If I check the event viewer, the msiintaller exits gracefully and states that Product: Adobe Setup -- Configuration completed successfully. But it's not installed?I reinstalled CS3beta and reactivated it, as I thought this might have been an issue, so I deactivated and went the the whole process again including downloading the 400 mb update file.The log file in the /common files/installer is generated and my source files are on the same volume. I'm now wondering whether my AVirus application might have something to do with it, but every other adobe application installs without a hitch.The mind boggles!

Things i've been doing before it miraculously didn't vanished were: using mirc, msn, firefox with lots of tabs, using windows installer cleanup and removing adobe setup, trying to open setup.exe with poweriso 3.7 (i know i was frustrated), then i doubleclick setup.exe and it didn't disappeared.I know im not of much help, but i want to tell you that there is hope to that issue.

From those humble beginnings comes my all time favorite windows applet, the venerable Task Manager. Task Manager was introduced with Windows NT 4.0, and although it has changed little in the intervening nine years, it hasn't needed to. Unlike virtually every other Windows OS applet of similar vintage** I still use it every day. That's a testament to how well Task Manager was originally designed.

I have a windows service (Serv.exe) running as LocalSystem, at a certain point it wants to show the logged-on user that it is processing data, therefore I CreateProcessAsUser(Display.exe) which is a C# Windows Form that display information (this all works perfectly fine).

Note that if --dhcp-option is pushed via --push to a non-windows client, the option will be saved in the client's environment before the up script is called, under the name "foreign_option_n".--tap-sleep nCause OpenVPN to sleep for n seconds immediately after the TAP-Win32 adapter state is set to "connected".This option is intended to be used to troubleshoot problems with the --ifconfig and --ip-win32 options, and is used to give the TAP-Win32 adapter time to come up before Windows IP Helper API operations are applied to it.--show-net-upOutput OpenVPN's view of the system routing table and network adapter list to the syslog or log file after the TUN/TAP adapter has been brought up and any routes have been added.--block-outside-dnsBlock DNS servers on other network adapters to prevent DNS leaks. This option prevents any application from accessing TCP or UDP port 53 except one inside the tunnel. It uses Windows Filtering Platform (WFP) and works on Windows Vista or later.This option is considered unknown on non-Windows platforms and unsupported on Windows XP, resulting in fatal error. You may want to use --setenv opt or --ignore-unknown-option (not suitable for Windows XP) to ignore said error. Note that pushing unknown options from server does not trigger fatal errors.--dhcp-renewAsk Windows to renew the TAP adapter lease on startup. This option is normally unnecessary, as Windows automatically triggers a DHCP renegotiation on the TAP adapter when it comes up, however if you set the TAP-Win32 adapter Media Status property to "Always Connected", you may need this flag.--dhcp-releaseAsk Windows to release the TAP adapter lease on shutdown. This option has no effect now, as it is enabled by default starting with OpenVPN 2.4.1.--register-dnsRun ipconfig /flushdns and ipconfig /registerdns on connection initiation. This is known to kick Windows into recognizing pushed DNS servers.--pause-exitPut up a "press any key to continue" message on the console prior to OpenVPN program exit. This option is automatically used by the Windows explorer when OpenVPN is run on a configuration file using the right-click explorer menu.--service exit-event [01]Should be used when OpenVPN is being automatically executed by another program in such a context that no interaction with the user via display or keyboard is possible. In general, end-users should never need to explicitly use this option, as it is automatically added by the OpenVPN service wrapper when a given OpenVPN configuration is being run as a service.exit-event is the name of a Windows global event object, and OpenVPN will continuously monitor the state of this event object and exit when it becomes signaled.