Current [TestBuild] v0.0.0.90 – Download
NOTE: the download may not always reflect the current version, however it should update to the most current version available during the first launch, prior to first-time setup.
Learn about the d7x “Alpha” series and the overall product direction here. Only d7x subscribers (meaning current d7II subscribers with active subscriptions) may test d7x Alpha.
Also, please stay tuned to the d7x Alpha Youtube playlist for demo and how-to content (be sure to subscribe to our channel for update notifications!)
PLEASE NOTE: “TestBuild” indicates the product is not fully tested, and usage in a production environment is not supported.
When possible, please use d7x to submit bug reports via the ‘Main‘ menu > ‘Create/Submit Bug Report‘ option. Please submit any manual bug reports using the form available at the bottom of this page!
Recommended Method: Place d7x v0.0.0.x.exe inside an existing directory with a registered/working copy of d7II.exe, and it will use the existing resources from that copy of d7II including the registration information. This should NOT interfere at all with regular d7II.exe operation or configuration files if it became necessary to use. See the note below on d7II and dCloud Compatibility for more information.
“Fresh Install” Method: Extract/Run d7x v0.0.0.x.exe and register it. It is strongly recommended to register d7x (or any fresh download of a d7x or d7II product) by using the Browse button to find/import your existing d7II\Config\Reg.Settings.dat file, which ensures the exact same “Technician Password” is used; see the note on the Technician Password below for more information.
100% compatibility exists between d7II.exe and d7x.exe (within the same folder structure) which is useful for testing in live environments and during transitional phases to release builds that replace d7II officially. There are two caveats:
1. It is important to remember that d7x.exe (meaning any version, e.g. “d7x vx.x.x.x.exe”) serves as a replacement for d7II.exe, therefore you MUST NOT run them both at the same time, not even from different folders or drives!
2. Also you must ALWAYS “End Session” from d7II if it has run on the system at any time prior to running any d7x.exe version. End Session is normally performed as if you were done with a repair/cleanup/removal/etc. “session” on a client’s PC, and ready to remove your tools.
In fact, all builds of d7x (and the previous “d7IIx” builds from the very first release) are compatible with existing d7II config/files/directory setups, and can be run from inside the same folder as d7II.exe itself (with the caveats mentioned above) while sharing the same d7II owner information and dCloud account.
NOTE: Depending on version, running both the d7x and d7II process simultaneously may not be possible, even from different paths. With either d7x or d7II, the second process instance you launched would recognize the existing process, and submit to the primary instance by terminating itself. This behavior is not guaranteed between the differently named apps, so please do not rely on it.
Further, when d7II session data is found in the registry, a new d7x process will run the existing d7II.exe and terminate itself (even when the process isn’t running, but the d7II.exe file exists.) If the d7II.exe file does not exist, d7x would continue but still use the existing set of app/config/report folders already determined by the previous copy of d7II. In this case d7x.exe would use the deleted d7IIx.exe’s session folders, which isn’t desirable (to fix, End Session from d7x before relaunching the same d7x.exe file again to start a new session.)
End Session is NOT a limitation with d7II.exe running after a previous instance of d7x.exe, which presents a major benefit. Because d7x currently operates using active ‘Session’ data in the exact same d7II format and location, therefore if at any point during a session/repair/”Auto Mode” you encounter a bug with d7x, you can shut it down or discontinue usage after a crash (the point being, do not “End Session” from d7x) and simply run d7II.exe instead to finish the job, from the same folder as described here (it should pick up exactly where the d7x.exe left off, even if a stall/crash occurred in the middle of an “Auto Mode” or other customized d7II-based action.)
d7x will not change the way that it handles the existing d7II config settings/definitions system/operational files, and therefore much of the d7II code involving the handling of these files is still in use. All .\Modules\*.* files are still in use and expect everything to be the way it is with d7II. These modules are the smaller programs existing as separate .exe files in the d7II\Modules subdir, which perform specific functionality outside of the main d7II.exe file. Over time all d7II modules will be replaced as they are either integrated into the main d7x.exe, re-written entirely, or retro-fitted with d7x Platform code and moved elsewhere (e.g. inside the “\d7x Resources” subdir) to preserve at least a co-existence with d7II which should remain usable as a backup, until it is replaced entirely by d7x as a stable and official update.
The very first time d7x or d7II.exe is launched without a registration file and registered by the owner, a case sensitive “Technician Password” is created at the registration prompt for use with the product’s various password protected options, which also serves as an encryption key for your customized d7II configurations when stored in the dCloud portal or on your own self-hosted FTP server.
If a different “Technician Password” is accidentally used when registering any new copy of a d7II or d7x product, it will cause data previously encrypted by d7II and/or d7IIx (such as your dCloud/FTP stored d7II configurations and branding customizations) to be unreadable by this and other copies of d7II or d7IIx, including the SFX Mini tool used for remote deployment.
For this reason, it is strongly recommended to register d7x (or any fresh download of any d7II product) by using the Browse button at the registration prompt to find/import your existing d7II\Config\Reg.Settings.dat file, which ensures the exact same “Technician Password” is used.
While you may copy/paste your registration information manually, you must be certain to type in the exact same “Technician Password” (case sensitive) to avoid issues in the future. Although we could decode the password from your unencrypted settings file (if you had one available to send us) we cannot retrieve the password from an encrypted configuration file, either on our servers or in your possession, since that very password was used to perform the encryption!
Release Notes and Known Issues
New ‘Config Mgmt Portal‘ (first item under the ‘Server’ menu) combines the separate dCloud/Self-Hosted FTP portals, and rewrites all server communication functionality with regard to config sets and definitions (note custom apps and reports storage Self-Hosted features which did not use the ‘portal’ type interface are still running under d7II code.)
New d7x Remote Deployment Tool (aka ‘d7xRDT’) can be created in the Config Mgmt Portal (above.) d7xRDT is the new implementation of d7II’s ‘SFX Mini‘, it is re-coded from the ground up, and although a little larger than before, it does enable more functionality. While new features are technically still on hold, this release adds a few improvements (over d7II SFX Mini functionality):
- New password prompt option during extraction
- Created using your custom branded application icon (as configured in d7x/d7II, else the default applogo.ico is used)
- Using elastic IPs in place of hostnames to resolve dCloud connectivity issues in situations where a particular ISP creates an issue with DNS or hostname based filtering.
- Capable of connecting to a d7x based “dCloud” server (not yet implemented) which uses SSL communications and can use HTTPS for login and uploading, allowing full dCloud communication, while bypassing any network restrictions on FTP protocols even over SSL channels.
- Note d7xRDT only works with d7x and is not actually able to download d7II.exe, so it cannot serve as a replacement for the current d7II SFX Mini to deploy d7II remotely.
KillEmAll v5 has been integrated into the core d7x binary, replacing the previous d7II based version of the program. (It has not been included as a separate/stand-alone executable.)
- New: should correctly save logs to the d7II Reports directory. This may does not yet include automated saving of file details when viewed through the file inspection window.
- Previous d7II/KillEmAll options for ‘Google’ web searches, VirusTotal uploads, file deletions/renames, etc. etc. are not yet available through the interface or the through the file inspection window.
- The previous ‘Suspicious Files’ search is also not available, but a more complete implementation (file system scan only) is found in d7II’s dFunk module used for manual inspection of the file system and registry.
- The previous version of KillEmAll with most of these missing features is still automatically downloaded as a separate exe along with other d7II modules, but the separate exe is and has always been a slightly older implementation of the internal version used in the last version of d7II, and will miss any included automatic reporting features through d7II.
- KillEmAll v5 also uses a new engine for user-created definitions enabling some new possibilities, see these pages for more:
Under the hood (sort of):
- All areas of config/definition storage (dCloud/Self-Hosted FTP) and sync not part of the new user interface were also replaced entirely with new d7x code. This did bring a few small extras to the user experience, as evidenced by the optional startup prompt shown here. This existing d7II feature used to merge definitions during a new session start was expanded to offer a download only option and a description of what the “merge” actually does (it’s even combined with the config prompt entirely, should that also have updates available.)
Note: the data crunching part of the definitions “merge” is still handled by d7II code (in fact via the dFunk.exe module) as before, but d7II.exe’s involvement in determining updates, retrieving the current defs, and putting updates back on the server was replaced entirely with new d7x code.
- v0.0.0.90 adds Windows 10 to custom app platform/OS restriction settings. If not configured, behavior should not change. Backwards compatibility note: This is the only area in d7x configurations where d7II may (and likely will) erase the setting entirely when used to edit the same custom app configuration.
- Elongated username/password input fields on the FTP Servers tab. Did not check/fix tab order there, but I will!
- UTC Adjustment removed from Config > Regional Settings on first tab which was used in converting various dates from UTC such as Windows event log entries when viewed through the internal d7x Event Viewer (the adjustment was used only in d7II.)
- When moving reports to your Self-Hosted FTP server in d7II, failures can occur for a number of reasons that didn’t trigger an error prompt (or didn’t change a success prompt) such as invalid credentials. Currently FTP transfer errors should be accurately and consistently reported, including some detail about the actual problem.
- Now automatically corrects the desktop shortcut target (to the reports path, optionally created during Start Session) if the reports path changes for any reason…
- Added Windows 10 recognition on System Info tab (which also resolves the annoyance of the Windows 8.1 Update 1/not installed alert on Windows 10)
- Removed “Automatic Updates are Disabled” check from startup alerts on Windows 10, since the update setting (and it’s associated Windows user dialog) no longer exist in Windows 10.
- Some “Offline” tab functionality may be disabled as functional issues are expected…
- The optional/manual user update functionality familiar in d7II was removed in current d7x Alpha builds, which automatically manages updates without user involvement. Optional updating will be added back to the program when final release builds are available (allowing the user to opt-in for ‘FastTrack’ builds.)
- Both d7x and d7II (Final) require Windows XP SP2 and recommend SP3; full support for Windows XP SP1x/2 and below may be implemented at a future time. If you find yourself working on an XP system without at least SP2 that you must repair it before you can update, d7II v3.6.4 is still available and is more than competent for the job! Simply download to your current d7II/d7x folder and run from there.
The current release should fix all known issues with any previous release, except:
- The “System Info” tab’s “Alerts” list should have all alert headings in bold type, which may not display as expected.
- Various references to “<AppName>” should reflect “d7x”
- Some web links initiated from d7x may prompt you twice before opening the link.
* Please report if you experience this issue: During the first run in a session, d7IIx may crash when trying to launch regedit.exe (e.g. from “Windows” drop down menu) without any error message from either d7IIx or Windows, however all subsequent usage functions as intended. The issue may only occur when no alternate registry hives were actually loaded prior to launching regedit.exe (which would be the case on a system with only one user account…) This is the result of a new experimental multi-threading routine used when launching regedit.exe, which waits for you to close regedit.exe before attempting to unload registry hives.
- Fixed: lower ticker msg (main UI) not displaying urgent news (e.g. CCleaner fiasco)
- Fixed: some web links initiated from d7x prompt for confirmation twice before opening the link when configured to use the system default browser (not an external/portable or the d7x based browser)… Note the “fix” here may cause the same issue for some links when an external/portable or the d7x based browser is configured; this is currently listed in the Known Issues section.
- Fixed: Weird sticky “on top” window z-order when launching d7x application windows (e.g. the Internal Windows Event Viewer) by double-clicking items in the System Info tab’s Alerts column.
- Fixed: “Check Event Log” and “Check Auto-Start Services” alerts were broken in the last few builds.
- Fixed: “hwpolicy” and “dam” no longer trigger the “System Device Issues!” alert (their status codes always indicate what would be an issue for any 3rd party driver, however code 31 seems to be just as normal as code 0 for these particular built-in Windows devices…)
- Removed: Config option to use dCloud SMTP (feature not available since earlier d7II releases.)
Previous issues from the “d7IIx” named builds:
- The newly integrated KillEmAll v5 currently did not populate results for whitelisted items ignored during a scan.
- d7IIx encountered several failures related to downloading/merging internal definition files from dCloud and more from Self-Hosted FTP.
- d7IIx did not restart automatically after Windows has been restarted (observed intermittently on a well used Windows 10 64bit test environment…)
- d7IIx did not restart automatically after downloading a config from dCloud/FTP (observed intermittently on a well used Windows 10 64bit test environment…)
- d7IIx reported crashing on a previous startup when restarting itself for certain reasons (such as updating it’s configuration after download from dCloud/FTP) even though it didn’t.
- The “Passed Checks” column on the “System Info” tab is truncated to one entry, and all headings in the alerts column should be in bold type, but aren’t.
- Certain multi-line displays on the ‘System Info’ tab, specifically the Alerts column, may be limited to two lines despite more information being available.
- User registration information stored in the Config\Reg.Settings.dat file was not saved correctly when entering/exiting the d7II config multiple times consecutively, causing a registration prompt on a subsequent d7II launch.
- May lockup with “Adding System Tray Icon” in status bar when Enable Shutdown/Restart Prevention is checked in your d7II config (consistent on the affected systems.) Remove the line “StartupShutdownPrevention=1” from your “Config\d7II.ini” file to work-around the issue.)Replacement of Task Manager with Process Explorer via d7II/x configuration setting stuck permanently; created by an IFEO, in fact removal of any IFEO was not previously functional.
- Some 3rd party tools (mostly used with reporting functionality) were accidentally downloaded to the root d7IIx directory and not the \3rd Party Tools dir.
- May not download/extract many custom apps properly if used by internal functionality (e.g. certain Sysinternals/Nirsoft utilities) resulting in the appearance of corrupt downloads, namely .zip files may have been named as .exe files during download, therefore no extraction is performed. Since the .exe is actually a .zip, when the file was executed (whether by d7IIx or manually from the 3rd Party Tools dir) it would fail to launch with various errors (depending on the specific Windows platform/architecture.)
- Branding (your company name/logos) may not function as expected…
- Anything requiring d7IIx to install itself as a system service MAY fail on some systems… This includes, but is not limited to:
- Launching itself and other processes under the local system account.
- Recovery for auto-start/Auto Mode while running custom apps that would normally terminate other processes, including d7IIx.exe
While these issues below were reported but not duplicated in our testing, they appear to be resolved, and may relate to other resolved issues.
- On some systems, may not process startup behaviors (occurring at each d7II start) nor start/end session configuration. (Reported from Win10 64bit, but consistent only on one PC in particular.)
- May lockup when asking for a password on d7II startup (if password protected startup is configured, consistent on certain systems…)
- The CPU utilization display (top banner) may not appear on systems it would have otherwise (it normally wouldn’t appear only on unsupported systems.)
- On a PC where d7II.exe or d7IIx.exe has not previously created a session, you must enter a ticket number in this prompt, else the screen will reappear without prompt and without loading the main user interface.
Some issues discovered may or may not have occurred in the final release of d7II v3.6.86, but these issues were discovered while investigating ported code…
- Fixed a minor issue where system restore points created from the “Windows” drop down menu were created using a generic name, not the one you typed in the prompt.
- Fixed dUninstaller bug: failure to apply the proper silent uninstall switches when processing installers created by Inno Setup.
- Fixed DataGrab bug: failed to create a registry export of ODBC settings from an offline OS/partition in some circumstances.
- Fixed issue in multiple functions used for both active and offline OS partitions, where a 64bit OS partition may not have been detected properly affecting functionality dealing with directory structures such as “Program Files” vs. “Program Files (x86)”
Small issues may be submitted with detailed debug information directly from d7x via: ‘Main‘ menu > ‘Create/Submit Bug Report‘ option.
Please note that a valid email address is required when requesting a response, and you must also use this to configure d7x’s SMTP server capabilities in order to send email (we do not provide an SMTP server for you “under the hood” as d7II once did, due past issues with reliability caused by email security and spam filtering services in use by various ISPs.)
Larger issues involving app crashes or those requiring d7x (or Windows) to restart cannot be submitted via the in-app method above, and must be submitted here. Although we realize we are asking a great deal of detail on your part, the information accuracy even to the smallest detail is often vital to the efficiency and outcome of our continued development efforts.
We encourage you to only submit unique issues one time, after verifying they are not covered in the “Known Issues” section above (please confirm your issue is not covered above before submission!)
Please do not use this form to suggest new features or functionality, we prefer suggestions on our forums at the customer service portal, where your post is public and can be seen by others who may have similar ideas.
Join us for live tech chat, product questions, support, and technical training right here!
Both Foolish IT customers and non-customers alike are welcome to discuss anything Foolish!
d7x (Alpha) September Update for d7II subscribers – Latest update includes a NEW d7x Remote Deployment Tool (d7II SFX Mini), a NEW Config Mgmt Portal, and more for testing! This latest d7x Alpha “TestBuild” replaces the “d7IIx Alpha” versions opened...
CCleaner (Piriform) Malicious Code Breach! d7x/d7II/dSupportSuite Users Take Notice! Update: These articles also came out yesterday, unfolding some plot twists...