Current [FastTrack] v220.127.116.11 – Download
The d7x Manual (this page) is primarily intended for users familiar with d7II who have updated to d7x. First-time users of d7II should see the d7II Quick Start Manual which also applies to d7x for first-time setup and usage.
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.
Please keep up with current information and announcements via our newsletter and blog/RSS feeds, and subscribe to our Youtube channel for videos and upcoming/on-air notifications of the Foolish Tech Show! Please see the “Links (All d7x/d7II Resources and Information)” section below for these and other valuable links!
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!
NOTE: The information below is intended for existing users who already have d7II setup and configured, and have now updated to d7x. First-time users of d7II should see the d7II Quick Start Manual which also applies to d7x for first-time setup and usage.
(Recommended) d7II In-App Method: Update via d7II’s internal update mechanism (d7II should alert you of an update to d7II v3.6.87). Upon relaunch, d7x should show the message box to the right, informing you that this is the update to d7x.
Notes: (d7II In-App Method)
#1 (non-issue) Please be aware that the update may appear to stall, however d7x is downloading updated dependencies silently. Currently the initial UI/splash screen when downloading some dependencies is not displayed, but we plan to correct this issue with a future d7x update.
#2 (d7II update settings) the d7x update process will alter your d7II configuration as necessary, in order to disable the d7II automatic update settings, so that you may use d7II.exe unhindered by forced updates, should a problem with d7x arise.
#3 (d7II.exe v3.6.87) d7x will attempt to update the existing d7II.exe to an actual d7II.exe, which has been altered only to increment the version number to v3.6.87, in order to satisfy update notifications if/when using d7II.exe in the future.
#4 (potential error extracting d7II.exe v3.6.87) Some users have reported an extraction error during the update, which may have left a zero byte d7II.exe file instead of the expected file. If this occurs, please manually delete the zero-byte d7II.exe file if it exists, after which the updated d7II.exe files can be downloaded from within the d7x Main menu > Check for Updates prompt, or manually via this link.
(Alternate) Manual Update Method:
Place d7x v0.0.0.0.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.
NOTE: This update method does NOT alter the d7II update settings as is done automatically in the recommended method above.
(Alternate) Manual Download Method:
Download the zip file, extract/run d7x v0.0.0.0.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.
Notes: (All Methods)
#1 (non-issue, temporary) SSL Certificate Prompt: Currently all methods may receive several certificate warnings during the initial download of certain d7x requirements (see pic.) This is currently expected behavior due to our server’s SSL certificate, which is assigned only by hostname/domain, and not IP address.
The prompt should not be triggered with d7x Platform based server communications (which will perform additional verification on the certificate) after the initial requirements are retrieved, however some exceptions may noted affecting various in-app downloads from our servers for d7II based modules or dependencies. If you notice these prompts after initial d7x setup/update from d7II, then please let us know where the prompt occurs for you.
Background: In current d7x builds, all existing d7II functionality that would communicate with our servers is subject to an automatic IP address substitution for hard-coded hostnames, as well as forced SSL. This was done to resolve issues with some ISPs and UTM configurations that from time to time have been known to accidentally blacklist our hostnames, and it will trigger the prompt in d7II functionality not yet adapted to newer d7x Platform download methods.
We plan to address this soon not only with d7x updates, but with a new SSL certificate for our download servers to cover all the bases, although we do not expect it to affect much more than the update/dependency process.
#2 (d7II.exe v3.6.87 and v3.6.4) The final d7II based .exe files and their dependencies can be downloaded within the d7x Main menu > Check for Updates if missing from the root of the d7x directory, or manually via this link.
100% operational compatibility exists between d7II.exe and d7x v0.0.0.0.exe on the same PC, from any folder, or within the same folder structure as d7II.exe (while sharing the same d7II owner/account/dCloud/Self-Hosted FTP) with two caveats:
1. It is important to remember that d7x.exe (meaning any version, e.g. “d7x v0.0.0.0.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.
100% configuration compatibility exists to read and apply config settings from d7II.exe –> within d7x v0.0.0.0.exe
d7x uses all d7II settings appropriately, even where d7II did not (some settings linked to features that were not functional in d7II will now operate properly in d7x, causing some minor but noticeable changes in behavior.)
* For example, the “Pre-Download” setting removed from d7II (due to operational issues) is once again functional in d7x; therefore if the d7II configuration was saved when the feature was available, it will take effect in d7x to download any missing custom apps (including those internally used for the selected functionality) at the beginning of an individual auto mode, or at session startup depending on how it was configured.
Other behavioral changes may be discovered, since the d7x Platform code has resolved a number of unknown or unintended behaviors with d7II code that we just won’t know about until they are found (which isn’t likely to be very soon since d7II is huge with a vast number of different features.)
99% configuration backwards compatibility exists to read and apply config settings from d7x v0.0.0.0.exe –> within d7II.exe
Some config settings have been modified in d7x, therefore changes from the d7x interface may not always be reflected or obeyed in d7II. We expect this to be the case for more in the future, soon moving to 0% backwards compatibility for config settings. Of course any settings related to newer d7x features are already not read by d7II.
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!
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.
d7II.exe will resume whatever you were doing with d7x prior to a stall or crash, and even a full auto mode
should resume as if Windows or d7II had only restarted during the process.
But first, please keep these two things in mind:
1. Please try d7x again, it may not have “failed” to perform the task, but only failed to “re-launch”
or “stay active” during the running of a custom app (if those apps are designed for tasks of their own
that interfere with d7x’s operation.)
2. Ensure the d7x process is NOT running, reboot the PC (may not be necessary, but helpful), and run
the older d7II.exe, which will pick up on d7II style session data (written by d7x during it’s operations
for backwards compatibility.)
Note that you can’t switch back to d7x until you End Session in d7II, but in order to properly preserve
session data and reports, you may safely finish your work with d7II.exe entirely on that system.
Newsletter, Blog, and RSS Feeds
Manuals and Information
Additional Subscriber Benefits (dMZ Private Access)
Community & Search
Release Notes and Known Issues
- Added: Support for Windows 10 (minor differences from Windows 8.x) in “Restore Default Start Menu LNKs” repair function.
- NOTE: Offline tab functionality may not be fully functional in this release. Please continue to use d7II.exe for all Offline related functionality (including usage from a ‘Tech Bench’ PC and/or WinPE based boot disk.) Obtain the final d7II EXE files via the Main menu > “Check for Updates” (click YES to download via the prompt; if you already have them, there won’t be an option…)
v0.0.0.94 and .95 (Oct. 24th, 2017)
- d7II.exe updated to v3.6.87 (version increment only) to satisfy future notification prompts, and made available for use as a backup in the event of d7x failure. This should be done automatically when updating to d7x from d7II.exe, but if you aren’t updating from d7II you can always download this via the prompt using the d7x “Main” menu > “Check for Updates” option, or use this link. UPDATE: Some users have reported d7II.exe as zero byte after an update to d7x is initiated from within d7II; in this event, please delete the zero byte file and then re-download d7II.exe via the method above.
- NOTE: Offline tab functionality is not fully functional in this release. Please continue to use d7II.exe for all Offline related functionality (including usage from a ‘Tech Bench’ PC and/or WinPE based boot disk.)
v0.0.0.92 (Oct. 18th, 2017)
- Auto mode and “Full” auto mode code/flow (nothing “new” in the user experience, unless there are problems!)
v0.0.0.90 (Sept. 22nd, 2017)
- Added 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.)
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.
- 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 “Installed Date” area on the System Info tab in Windows 10 reports correctly, however Windows 10 modifies this value with every major update. We are investigating other methods to obtain the original installation date.
- 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:
- All “Offline” tab functionality (used in working with OSes on partitions other than the active/system partition, e.g. from ‘Tech Bench’ PCs or WinPE boot disks) is not expected to function as desired (failure to accomplish tasks, auto mode stalls/freezes, etc.)
- dUninstaller functionality utilizing definitions for deleting registry entries and values is bugged and when definitions exist it can indefinitely lock/freeze the d7x process.
- Auto Mode will stall when using the “Safe Mode w/Net Mod” used to keep Windows in the “Safe Mode with Networking” state across reboots in Auto Mode.
- d7x lower status bar may report “Idle…” when busy (or an idle/display message) during an Auto Mode. Specifically, Malware Auto Mode configurations using KillEmAll settings/options at the top can trigger this behavior, though it may also be caused by various other reasons in any Auto Mode. Subsequently, clicking anywhere within a d7x based user interface will trigger the “Not Responding…” Windows message. In this case, d7x isn’t updating the user interface appropriately, which causes both the status bar “Idle…” message as well as the Windows/app unresponsive behavior when the user initiates any type of interaction with one of d7x’s windows. Please be assured that d7x is most likely doing what it should be, and therefore d7x should be left undisturbed for a reasonable amount of time (even in a state where the user interface is unresponsive) based on the last action performed or desired, in order to determine if there is any issue (beyond the broken UI status update.)
- The “Run” menu option “Restart This App (Safe Mode)” does not restart d7x as it shuts down. It does set d7x safe mode, so subsequently relaunching the d7x EXE file manually will start in d7II’s safe mode user interface. Note that d7II’s safe mode is a minimalist UI without System Info tab, which would run faster, have fewer issues on systems with busted WMI, and is resizable unlike the standard interface.
- The “System Info” tab’s “Alerts” list should have all alert headings in bold type, which may not display as expected.
- Some web links initiated from d7x may prompt you twice before opening the link.
Default Configuration Settings:
Some config settings used in d7II may not be interpreted properly by d7x (to apply default behaviors) when the settings don’t already exist. This can result from running a config created with an older version of d7II and then using that via the SFX Mini for remote deployment (always an issue with previous d7II updates and outdated configs deployed via the SFX mini.) It can also simply result when new config settings are introduced and the Config screen is subsequently loaded and saved (along with the defaults for new settings.)
In fact, you can expect this to happen as you use d7x even right now without any actual d7II behavioral changes, since the d7x Platform code has resolved a number of unknown or unintended behaviors with d7II code that we just won’t know about until they are found, which isn’t likely to be very soon since d7II is huge with a vast number of different features.
“Pre-Download” Setting for Custom Apps:
One setting for the “Pre-Download” of auto mode apps (beginning during a session or an individual auto mode, rather than waiting until the app is actually used) was introduced later in d7II v3.x and then removed in the final versions of d7II. If not configured during that d7II v3.x release, the default behavior of the Pre-Download setting (to download all apps before starting the Auto Mode process) will take effect in d7x. This may surprise many users as a “new feature” that really isn’t new, but more like a bug fix that enabled older features to function properly. The returning feature can be changed/disabled via the Main (top left textual menu) > Config > Config (Main App Settings) > Custom Apps (tab) > Misc Settings (tab) > Pre-Download Options for Custom Apps (section) > and change “Auto Mode Start” to the “Disabled” option. See pic to the right.
* 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.
* We would like to give thanks to everyone contributing reports on any issues, such as Luke (developer of PC Repair Tracker) for both your time and attention with reporting various issues as well as new suggestions! (You can also thank Luke for the new Windows 10 platform restriction in custom app settings, added in an earlier TestBuild from October.)
- Fixed: Determined that the default a2cmd custom app was not downloading properly, which started but returned the error code for “aborted” before completion (still largely based on d7II code.) In order to resolve the issue, a different fail-safe download method was implemented (pure d7x download code, but without a UI/progress bar, to be added soon.)
- Fixed: Some custom apps running via batch file weren’t completing as expected (those launching other batch files or console-based exe files.) Note this also affected a2cmd, for which both fixes in this release address.
- Fixed: “Run Windows CleanMgr.exe” was previously freezing d7x and maxing CPU usage.
- Fixed: Some editions of Windows 10 32bit were incorrectly reported as 64bit (which may also have caused some functionality to fail on 32bit systems, although d7x will in many cases try the 32bit redirected paths when 64bit paths don’t exist.)
- Fixed: “Restore Default Start Menu LNKs” repair functionality failed to create missing shortcuts.
- Modified: Some users reported the Browse button doesn’t work on the DataGrab tab on some systems… could not reproduce, but tweaked code in an attempt to fix…
- Fixed: failure in right-click context menu item “Configure App / Function” not launching the config for that custom app or internal function within normal and safe mode user interfaces.
Non-Code Issues from the d7II Initial Updates (Oct 24th/25th, 2017)
- Fixed: Replaced a corrupted archive on our servers which was causing the update to fail with extraction errors…
- Fixed: Some users did not receive this message prompt notifying them of d7II/d7x compatibility during the update (an issue with the update settings on our server.)
v0.0.0.92 (Oct. 18th, 2017)
- Improved: Screen saver prevention did not disable with the config changes until restarting the app (improved from d7II)
- Fixed: Settings to “Hide…” the second line item descriptions/icons in task boxes for custom apps/internal functions did not take effect when d7x was first starting up (instead the settings were only taking effect when refreshing certain settings, such as after entering/exiting the config screen.)
- Fixed: When no internet connection is available, removed multiple download errors when running d7x, starting a new session, starting auto mode, etc.
- Fixed: You may not be able to change Auto Mode profiles if you have previously started an Auto Mode on that system, unless you first End Session (d7x should show a system tray/icon alert/balloon message during an attempt, which states that you can’t change profiles when auto mode is running… even though it isn’t… the work-around is to End Session and restart d7x.)
v0.0.0.91 (Sept. 26th, 2017)
- Fixed: various user interface and a few minor issues, such as references to “<AppName>” and a “d7II” should have displayed as “d7x” instead.
v0.0.0.90 (Sept. 22nd, 2017)
- 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.
v0.0.0.89 (Sept. 19th, 2017)
- 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.)
v0.0.0.88 (Sept. 18th, 2017)
- Fixed various minor issues from v0.0.0.87, related to the initial name re-branding from “d7IIx” in “d7x” v0.0.0.86 (Sept. 14th, 2017).
Previous issues from the “d7IIx” builds (Ending with v0.0.0.79 released on Aug. 12th, 2017):
- 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 the issues below (from early “d7IIx” named builds) 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 method of launching the Windows “About” dialog which caused scrambled text in the native Windows prompt (this is launched when clicking the “Installed Date” area on the System Info tab.)
- 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!
d7II to d7x update error corrected, please accept my personal apology for any disruption in usage! Please accept that I deeply regret any inconveniences you and...
d7x is officially updating for all d7II subscribers… d7II subscribers will notice their copy of d7II v3.6.86 now...