d7IIx Alpha – Known Issues / Submit Bug Report
Current Alpha Release: v0.0.0.72 – Download Here!
Note: the download may not reflect the current version, however it should update to the latest during the first launch.
Instructions for the current release:
Step 1: Extract/Run d7IIx v0.0.0.x.exe and register it. (You must have an active d7II subscription for usage.)
That’s it! Please submit any bug reports using the form on this page!
Note: It is strongly recommended to register d7IIx (or any fresh download of any 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 at the very bottom of this page for more information.
Alternate Step 1: Place d7IIx v0.0.0.x.exe inside an existing directory with a registered copy of d7II.exe, and it will use the existing resources from that copy of d7II including the registration information. It was previously recommended that d7IIx v0.0.0.x.exe should reside within the same dir as an existing/working d7II.exe, so using it in this way should NOT interfere at all with your regular d7II.exe operation or configuration files (not even during the same d7II session) provided the two different exe files are not used simultaneously.
- Now requires Windows XP SP2 at a minimum; support for Windows XP SP1x and below may be implemented at a future time.
- Update functionality from d7II has been disabled; d7IIx Alpha versions will currently auto-update themselves without user prompt.
- Debug output/log creation for troubleshooting purposes has been disabled entirely until further notice.
New for testing:
- KillEmAll v5 has been integrated into the core d7IIx binary, replacing the previous d7II based version of the program. (It has not been included as a separate/stand-alone executable.)
- You might expect that all modes including ‘report only’ would save logs to the d7II Reports directory; unfortunately that is not yet functional, nor is automated saving of file details when viewed through the file inspection window.
- Additionally, previous d7II/KillEmAll options for ‘Google’ web searches, VirusTotal uploads, file deletions/renames, etc. etc. are not yet available.
- 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.
Known or potential issues with this release:
NO MAJOR ISSUES are known at this time. Minor issues are as follows:
- The newly integrated KillEmAll v5 currently does not populate the list for whitelisted items ignored during a scan.
- d7IIx may or may not encounter several failures may occur related to downloading/merging internal definition files from dCloud/FTP (currently being addressed…)
- d7IIx may or may not not restart automatically after Windows has been restarted (observed intermittently on a well used Windows 10 64bit test environment…)
- d7IIx may or may not not restart automatically after downloading a config from dCloud/FTP (observed intermittently on a well used Windows 10 64bit test environment…)
- d7IIx may or may not report that it crashed 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.
* 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.
Previous release known issues: (RESOLVED in current testing.)
- 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
Previous release user reported issues: (never duplicated; may be resolved.)
- 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.
Submit a d7IIx Alpha Bug Report
Bug reports are encouraged on the current d7IIx alpha release for anything not covered in the “Known Issues” 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.
A valid email address and dCloud (d7II subscriber account) username is required to submit a bug report; the dCloud username may be automatically filtered for validity before accepting reports.
Note on the “Technician Password” used for registration:
When you registered your very first copy of d7II.exe, you would have created a case sensitive “Technician Password” at the registration prompt for use with the product’s various password protected options, which also serves as an encryption key for your 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 product including d7IIx, 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 d7IIx (or any fresh download of any 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. While you may copy/paste your registration information manually, 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!
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!