d7x uses a ‘session‘ concept, which you can think of as a “Repair Session” or “Malware Removal Session” where “session” could be substituted with “job.”

*** Always use the “End Session” button when finished with d7x on any system, even if you launched the software once, did nothing, and closed it.  The “End Session” button can seen as an option when clicking the red X to close the main d7x interface.  If that’s enough explanation, then you can skip the rest of this section, which explains what a ‘session’ is and what it does.

d7x will start a new session when launched for the first time, on any system that it was never previously used on, or where it has ended a previous session.  During this first run in a new session, certain temporary system modifications will take place, such as:

 * Creates registry entries necessary for operation for auto mode functionality with itself (remembering options after reboot or program restarts) as well as for exchanging settings and path information for external applications used with d7x, for scripting functionality, and for 3rd party applications that you may be using.

 * Applies whitelisting to Windows Defender (where possible) on d7x and subdirectories.

 * Applies group policy settings (if configured) such as Windows Update and even using a WSUS server on your local network.

 * Applies other preferences in Windows settings that you use to work on a system, such as showing hidden files, system files, file extensions, and more!

 * Creates a desktop shortcut to the d7x executable or the parent directory if configured (assuming you don’t just run it from a folder on the desktop…)

 * Installs right-click context menu items in Windows Explorer (the ‘shell extensions’) to be used for quick work with d7x on files in the file system.

 * Automatically run any scripts, d7x internal functions including creating system reports, or 3rd party applications that you have configured.

In order to remove these session specific settings (especially the Explorer context menus) you MUST use the “End Session” button on the “End Session” tab after you are finished with d7x on that system.

Alternately, the red X button at the top right of the app will give you the End Session option as well, executing the End Session options as configured on the “End Session” tab.

End Session can also be configured to perform other automated tasks, such as:

 * Email reports/logs to the tech.

 * Upload reports/logs to your self-hosted FTP, including a method to send reports to your customer ticket in the 3rd party PC Repair Tracker software.

 * Upload any configuration changes made during the session, either to our cloud storage or your self-hosted FTP.

 * Apply other settings changes to Windows.

 * Automatically run any scripts, d7x internal functions, or even install other 3rd party applications that you have configured.

 * d7x can also self-delete after the End Session tasks complete (this will delete the entire folder where the d7x .exe/files are located.) 

You could think of it as an “install” and “uninstall” however the terms are not correct in that d7x are portable applications, which can be run from anywhere with no installation package or process.  As such, you won’t find them in the installed programs lists of Windows Settings/Control Panel, and therefore there is no uninstall package to worry about.  Simply close the program a different way (End Session) when you are finished!

Those familiar with the original d7 may know that it performed many of these temporary system modifications at each program start, and also removed them at each shutdown.  This behavior was changed with d7II and now d7x to increase startup speed and mitigate other potential issues, as well as to add easy indicators for applying other permanent modifications that can be made as you have configured them (such as applying your custom branding to the operating system) but these aren’t applicable here.

Final Note:  When d7x is launched on a system, you cannot start a new copy of d7x from a different folder until you End Session from d7x.  d7x will always find and launch the d7x .exe that was originally launched on that system, terminating itself on success.  This is by design, in order to properly preserve session data and reports, so that you may safely finish your work with d7x.exe as necessary without confusing files and settings from a different copy of d7x in a different folder.  This typically only impacts people configuring d7x on a tech bench system, where no repairs are being performed however multiple copies of d7x exist and are used for configuration from different folders.