d7x (PC Technician Software) – d7xTech.com (formerly Foolish IT) https://www.d7xtech.com Computer Repair Software - PC Tech Utilities - Malware Prevention Fri, 22 Jun 2018 16:09:34 -0400 en-US hourly 1 https://wordpress.org/?v=4.9.6 42914034 d7x v18.5.18.1 released with email/SMTP fix for those not using TLS https://www.d7xtech.com/2018/05/d7x-v18-5-18-1-released-with-email-smtp-fix-for-those-not-using-tls/ https://www.d7xtech.com/2018/05/d7x-v18-5-18-1-released-with-email-smtp-fix-for-those-not-using-tls/#respond Fri, 18 May 2018 22:12:57 +0000 http://www.foolishit.com/?p=14464 This release fixes an Email failure in SMTP configurations that use either the “No Encryption” or the “SSL only” option.  Those using TLS via the “SSL/TLS” or “StartTLS” SMTP settings were not affected by this issue.

Also fixed this release is the “Send Test Email” button in d7x Config which always returned a successful result, even if it failed to send.

]]>
https://www.d7xtech.com/2018/05/d7x-v18-5-18-1-released-with-email-smtp-fix-for-those-not-using-tls/feed/ 0 14464
d7x v18.5.7.1 Release Notes (with Custom App updates) https://www.d7xtech.com/2018/05/d7x-v18-5-7-1-release-notes-with-custom-app-updates/ https://www.d7xtech.com/2018/05/d7x-v18-5-7-1-release-notes-with-custom-app-updates/#respond Mon, 07 May 2018 22:50:29 +0000 http://www.foolishit.com/?p=14437 Today’s release adds only one notable improvement to the custom apps download capabilities, which facilitates the download of AdwCleaner using the improved non-direct URL option.  This was necessary when updating the custom apps package for this default app, as well as the Auslogics DD Portable which also needed a newer download URL.  The default custom app profiles are updated automatically and without notification.

Please Note:  v18.5.7.1 is NOT a ‘FastTrack’ build as it will be detected by previous versions, rather this version is actually a ‘Release’ build (which also fixes the bug in prior versions causing this issue.)  For this reason, the only update notification will come as an optional prompt when manually checking for updates (which will incorrectly inform you it is a ‘FastTrack’ build.)  Please update to this build in order to resolve the issue with FastTrack/Release build detections!

]]>
https://www.d7xtech.com/2018/05/d7x-v18-5-7-1-release-notes-with-custom-app-updates/feed/ 0 14437
d7x v18.4.28.0 Release Notes https://www.d7xtech.com/2018/04/d7x-v18-4-28-0-release-notes/ Sat, 28 Apr 2018 19:22:38 +0000 http://www.foolishit.com/?p=14409 Fixed an issue where d7x failed to start with the “System Mode” d7x Startup configured (d7x Config > Behavior tab > Startup Behavior) when d7x was started without all of it’s resources already downloaded, which is always the case when deployed remotely via d7xRDT.  One of the d7x Resources (d7xSvcWait.exe) is required for this mode to function properly.

Side Effects:  The next normal launch of d7x (non-system mode) on that PC would determine that a temporary d7x service was installed, and at this point it will be removed by choosing the “Abort” button.  See pic.  

FYI:  A good work-around that would’ve worked in this case to start d7x in normal (non-system) mode is to force the d7x startup prompt.  Do this by holding down the CTRL key while starting d7x (a great time to do this is after clicking OK on the UAC prompt that fires when you launch d7x), and then choose the “Normal Startup” option which would bypass the pre-configured “System Mode” option causing the failure.

 

]]>
14409
d7x v18.4.18.0 Release Notes (Updated to include all v18.x.x.x) https://www.d7xtech.com/2018/04/d7x-v18-4-18-0-release-notes/ Wed, 18 Apr 2018 16:04:14 +0000 http://www.foolishit.com/?p=14220 [Release Build] v18.4.18.0 

Download via the d7x Manual (or update by launching d7x.)

  • IMPORTANT:  If you haven’t read yet, d7x v18.2.3.0 and all previous versions will no longer self-update or recognize update availability.  Please see this post for more information including specific update instructions (copy the latest “d7x vx.x.x.x.exe” file into your d7x folder, delete the old version, and re-create your d7xRDT if one was used.)  Please accept a sincere apology for any inconvenience this may cause.   

New Features in d7x v18.4.18.0

  • Lock Screen and Unlock Screen:  These d7x features have been added to the list of functions available to assign to your custom list boxes in the main interface.  (from the Config -> Custom Apps tab, or the “Add App / Function” floating window, select either “d7x ALL Functions” or “d7x Misc”, then type “lock” or “screen” in the search box.)
  • Lock Screen:  Added prompt to verify that the tech knows the Technician Password before allowing the lock screen to be enabled.  This prompt will occur ONLY ONCE per session, and does NOT apply to the new custom Lock Screen option above when run during Auto Mode.
  • Config UI:  Custom Apps and d7x internal functionality (Custom Apps tab) now displays the detailed description in the lower pane when clicked on (so you don’t have to switch back and forth between the Edit/View tab and the Assign App tab if that’s what you’re doing…)
  • Config UI:  Improved search option on Custom Apps tab to include item descriptions for d7x internal functionality.
  • Config UI:  (Servers / Email tab) Added link to our software FAQ on the website to explain troubleshooting Gmail (specifically regarding MFA and the “Less Secure Application” Google options, which also links directly to them on Google the account site.)
  • Updated search engines:  (Config -> Browser/Search tab) Removed Scroogle (no longer in operation) and Dogpile (which at one time was worthy but no longer.)  Added Duckduckgo and Bing (for some reason…) Separated Google searches to specific English, Encrypted, and English/Encrypted options.
  • Mail Password Functionality:  Restored functionality utilizing Nirsoft MailPV.exe for mail password gathering functionality.  This was previously disabled when Nir updated the app to remove command line arguments, unless you had below a certain version of that .exe still in your .\3rd Party Tools directory.  Since then Nir has released new versions that re-enable command line arguments, but they must be downloaded from a password restricted area; d7x has been updated to download the new MailPV.exe from that area so it can once again function as previously expected.
    • New password protected download functionality was implemented for this feature, and although this is not yet available as a configurable option for other custom apps, expect that to be added to the custom apps configuration interface in a near future update.  

 

Bug Fixes in d7x v18.4.18.0

  • d7x and d7xRDT Crash:  Fixed a scenario where a semi-random crash would occur for certain users/configurations when either starting d7x or when saving the Config.  Since the issue occurred during d7x startup, it was also seen when deploying from the d7x Remote Deployment Tool.
  • d7x Slow to Close if…:  Fixed an issue causing d7x to close far more slowly depending on how long it was left running.  For example on an average system if left running on the tech bench over the weekend, it could take up to 5 minutes or more to close itself.  This was most notable when a self-restart or Windows restart was invoked from within d7x after it had run for an extended period of time, and mostly a problem for d7x cleanup routines if a Windows restart was invoked from outside of d7x (e.g. by the user or a custom app.)
  • Info Report / Product Keys:  Fixed an issue which caused an error “system cannot find the path specified” when generating an Info Report, specifically during the “Getting Product Keys” routine.
  • Client ID and Reports Directory:  Fixed:  Removed a temporary work-around (in place to resolve some FTP upload issues) which was creating these values after filtering out many non-alphanumeric characters, most visibly this replaced spaces with underscores.
  • Client ID/Ticket Number:  Fixed:  The “Client Name” and “Ticket Number” used in reporting were set to default values with each restart of d7x after the first session start, or any time the session start prompt wasn’t shown.  This caused issues or failures in uploading reports using incorrect filenames particularly when uploading for PC Repair Tracker integration (unless prior to uploading reports you manually invoked the session start prompt by clicking the “# / Name” label on the System Info tab, which did reset these to the proper values.)
  • Lock Screen:  Fixed Lock Screen interface not displaying the password prompt when the unlock button was clicked, and also not resizing to cover the entire screen.
  • Config UI:  Fixed issue where all hovering the mouse over any checkbox on the “Behavior/Updates” tab always displayed the “Activation Check” details in the lower description pane instead of the details for that specific item.
  • Config UI:  Fixed issue where search option on Custom Apps tab sometimes displayed results without the search term.
  • FTP Upload Failure with Integrated Apps:  Fixed an issue where uploading from the Integrated Apps tab (under the Config -> Custom Apps tab) would fail to upload files such as dSupportSuiteSetup.zip; also the FTP Upload functionality now accepts .exe as well as .zip files as might be expected.
  • Space Freed / 0 bytes:  The v18.3.x.x releases reported 0 bytes deleted during any Maintenance based operation or when temp files would be deleted; the 0 byte message applied to user interface prompts as well as the Work Report, but was not respective of the space that was actually freed (as all features were working properly, only the reporting of freed space was incorrect afterwards.)
  • Disable Windows Defender:  Restored the functionality to disable Windows Defender (Config > Behavior tab > General Behavior section) which was not working properly depending on the build of Windows 10 and possibly 8.x as well, by implementing some new methodologies to accomplish the task.
  • d7x Desktop Shortcut:  (Config -> Session) is now corrected automatically after updating to a new version of d7x (due to the differing filenames.)

 

Other Changes in d7x v18.4.18.0

  • Offline mode functionality has been removed entirely pending a rewrite, and will be re-introduced in a future update as separated from the current main interface.  The visible Offline tab remains in the current build but functions as described below.
    • Offline mode functionality is used in working with OSes on partitions other than the active/system partition, e.g. from ‘Tech Bench’ PCs or WinPE boot disks.
    • Please continue to use d7II.exe for all Offline related functionality.  With each new launch/instance of d7x, on every first click of the Offline tab you will be prompted to run d7II instead (from d7x\d7IIv3) which will download as necessary.
    • NOTE:  dFunk (aka MalwareScan) is NOT affected, so it can be launched via d7x itself without issue, or as a separate exe it can be launched by itself from the d7x\Modules directory (you would then point it to an offline OS installation by selecting the desired partition’s drive letter from the drop down selection box.)

 

d7x ‘Fully Loaded’ SFX

The ‘Fully Loaded’ SFX available for download from the d7x Additional Downloads section in your dMZ account has been updated to the latest version, and includes the latest Custom Apps configurations as well as some new custom Menu defaults for the d7x main interface (e.g. Links, Folders, Registry, Search.)

Please be aware this is a fully pre-populated and configured copy of d7x and is only for NEW configurations of d7x.  If you extract this to an existing d7x directory it will overwrite ANY existing configuration, including logo files, with the exception of your product registration and Technician Password.

If you wish to start over fresh using this configuration, it is highly recommended to extract this to a NEW directory and when running d7x for the first time, use the Browse button to import your existing Reg.Settings.dat file from an already registered copy of d7II or d7x, which contains your product registration and Technician Password.

Always remember:  If you run d7II or d7x on any system and do not use “End Session” to close it, running any subsequent d7x version from any other location will in turn launch the d7x .exe that was used to start the session, as well as use it’s configuration instead.  Always “End Session” when closing d7II or d7x on any PC you intend to use/configure multiple copies on, prior to launching the d7x .exe in any other location.

 

Changes in d7x v18.3.x.x

  • NewTechnician Password correction!  When extracting an encrypted config archive, d7x will now prompt if the technician password (used for archive encryption) is incorrect, allowing the option to retry as many times as necessary.
    • Previously when encrypted config extraction failed due to an incorrect password, d7x was launched with blank config triggering a first-time registration prompt on launch.  This has actually been an issue since d7 Premium with dCloud, but rarely a problem since typically no one changes that password.
    • By having few options in d7/d7II/d7x that require it’s manual input, this is why it can easily be forgotten and not become an issue for quite some time.  It usually takes a new major release (d7II, and now d7x) when those opting for the “clean download/setup” can bring this on with new configs created using different technician passwords entered during the initial registration process.
  • New:  d7xRDT v18.3.17.1 and above will self-update it’s own binary when deployed, to ensure server connectivity with updates as changes are required.
  • Fixed:  Failure to run scripts within custom app configurations that used the %scriptdir% variable to point outside of the 3rd Party Tools directory.  Possibly other cases were an issue resulting from the bug.  Further, some custom apps were failing without a download URL being configured.
  • Fixed:  d7x sometimes failed to restart itself along with Windows.  Previous versions ran shutdown code which removed the startup entry responsible for launching d7x after a Windows restart; this also stalled auto mode operation until d7x was manually launched again.
  • Fixed:  Issues and failures related to reboot options to put Windows in Safe Mode, including a failure with the custom internal functionality “Safe Mode w/Networking Mod” which is now working properly.
  • Fixed web links opening in the d7x internal browser despite being configured to use the system default web browser.
  • Fixed:  Starting with d7x v18.3.16.0 and d7xRDT v18.3.17.1 self-updating is once again functional.  All previous versions will fail to establish secure communications with our servers after Feb. 26th, 2018.
  • Change:  The d7x window’s title bar previously forced the version display, ignoring user preference (this is by design for TestBuild and FastTrack releases, but now temporarily removed in FastTrack versions until the first Release version follows soon.)
  • Change:  d7x v18.3.16.0 to d7x v18.3.17.1 do not completely force shutdown/restarts but allow waiting for apps to close within the Windows configured hung app timeout value (after which the system shutdown/restart is forced.)  While this change is as much of a feature as an issue in some cases, in others it should be reverted back to the old behavior soon, or allow for user configuration/prompt.  (Feedback on this change is appreciated.)
  • More was done, and more is to come…

 

Changes in d7x v18.2.x.x

  • New:  Config > Personalize contains two new settings “Display Config Name in Title Bar” and just under it “Include Config Date” will display the current config name and date used in the Config Mgmt Portal
  • Fixed:  The existing setting in Config > Personalize to “Display d7x Path in Title Bar” is now working again.
  • Fixed:   “Full Auto Mode” may repeatedly reload default settings for the “Audit” tab if d7x or Windows restarts for any reason, and the mode has already progressed to another tabs; the effect would be that the checked items will run all over again.
  • Fixed:  Zip reports for upload to FTP server (most notably used with PC Repair Tracker integration) may fail depending on your configuration.  The issue is resolved in our testing; please report any further issues.

 

Changes in d7x v18.1.x.x

  • New: Automatically assigns %computername% as the client %name% used in reporting. As a result, uploading reports (to FTP) for the current session will succeed without error when a client %name% is not set from the new session dialog (this dialog should also now appear by default in unconfigured copies of d7x.)
  • New: d7x FTP code replaces d7II FTP code for downloading custom apps stored on a self-hosted FTP server. (TODO: Replace report uploads still using d7II FTP code.)
  • Change:  Various d7II-specific code has been replaced with d7x-based replacement code. Affected areas include manipulation of user profile directories by various procedures, loading/saving file data, loading/saving of (d7II compatible) d7x configuration settings, and more. Benefits include stability with improved error handling, and speed with fewer disk read and especially disk write operations.
  • Changed7II v3.x files (when downloaded automatically) are now saved to the d7x\d7IIv3 subdir; the d7x\Config dir is also automatically copied there to separate config settings as d7x transitions to using newer features and settings not compatible with d7II.  We would prefer you to copy your d7x\Config dir to the d7x\d7IIv3 dir after settings changes in d7x (and also copy the d7x\Modules to d7x\d7IIv3 if definitions files are altered through d7x.)    See the “d7II v3.6.87 Update Information” section above for more details.
  • Change:  The “Start Session” config option “Automatically generate System Info Report” now checks Windows Activation for the report, even when Windows activation checks on Vista and above are disabled (also changed to become the new default) when loading the System Info tab.
  • Change:  Moving reports to a UNC path (via End Session tab/config) and emailing the reports are affected by new code replacements, which is in preparation for modifications and new functionality.
  • Fixed:  Audit and Tweaks Auto Mode were previously bugged and never triggered the flag to signal that they had completed all tasks.  As a result, changing the Auto Mode profiles (top right selection box) would fail with a user prompt explaining to stop the current task before switching modes.
  • Fixed:  KillEmAll (v5 internal) had improved kill routines that were terminating critical Windows 10 processes (one in particular caused UI issues in d7x, Windows itself, and other apps) therefore internal logic was improved/added for additional Windows 10 processes.
  • FixedWindows activation checks on Vista and above were occurring more than necessary; this is an issue on Vista and above because it is a slow process and causes the d7x UI to hang while it is running.
  • Fixed:  Some web links initiated from d7x may prompt you twice before opening the link.
  • FixedFab’s AutoBackup not launching AutoBackup6ProTrial.exe after download.  Improved detection of existing AutoBackup[x]Pro.exe files.
  • FixedIssue:  (Manual Resolution Available)  Fab’s AutoBackup button continues to launch the extract utility if any AutoBackup[x]ProTrial.exe files are found in a \3rd Party Tools subdir from previous d7II/d7x v17.x usage.  A fix is planned, but deleting the file will resolve the problem entirely, as well as enable the new Fab’s AutoBackup fixes to former functionality and new behaviors.  The issue is now resolved.
  • Fixed:  When a system was configured to use more than two DNS servers, the display on the System Info tab was not truncating the display info.
    • Remaining Issue:  Unfortunately the hover tooltip and lower status display is not displaying the full list of DNS servers.
  • FixedSession start tasks were not running when launched from d7xRDT (Remote Deployment Tool) as configured, including asking for client name/ticket number, installing context menus for explorer, creating the desktop icon, correcting time zone, etc.
  • FixedIncorrect reporting of drive space freed by temp file and maintenance routines (most routines were reporting available space after the cleanup, not space freed by the cleanup!) 
  • FixedEnd Session tab settings not loading from the d7x safe mode UI, as well as (re)loading on the normal UI every time the tab is switched back to End Session, and reloading again when actually ending session if triggered from the top right red X button, but after the button is pressed, negating any manual/temporary config change you may have made on that tab previously.
  • Fixed-ish:  Custom Apps and other integrated apps (e.g. Fab’s AutoBackup) stored on Self-Hosted FTP servers fail to download if located in the root FTP path (e.g. “/CustomApp.zip”) and not a subdir.
    • UPDATE:  See the first item in KNOWN ISSUES for a resolution.  

 

]]>
14220
d7x v18.3.16.0 and above are required for future updates; older versions will not recognize update availability. https://www.d7xtech.com/2018/03/d7x-v18-3-16-0-and-above-are-required-for-future-updates-older-versions-will-not-recognize-update-availability/ https://www.d7xtech.com/2018/03/d7x-v18-3-16-0-and-above-are-required-for-future-updates-older-versions-will-not-recognize-update-availability/#comments Sat, 17 Mar 2018 23:47:41 +0000 http://www.foolishit.com/?p=14132 This morning we released d7x v18.3.17.1 (yay!) just as it became obvious that existing versions will not update, and most any d7xRDT packages will also fail to download or launch d7x.

If you have d7x v18.3.16.0 or above, your copy should update to today’s release without issue; not so with any previous releases.

Affected Versions

 * d7x v18.2.3.0 and below will fail to communicate with our secure download site, including receiving even the notification of any new update availability.  The result is that it will never know updates exist.  d7x would also fail in debug submission uploads, although by using an email address with your submission (and checking the response requested option) it would still successfully make it to our support ticket queue.

 * d7xRDT aka Remote Deployment Tool of most any 0.x.x.x version that is out there will also fail to communicate with our secure download site, returning a simple download failure error and aborting.

Not Affected

* Communication with other servers is unaffected, including those used for registering the d7x software and by the dCloud system for config/definitions storage (which is also used by d7xRDT, though a somewhat moot point.)

* Communication with other software (e.g. CryptoPrevent) is unaffected.

Resolution

The most current download is always available at the top of the d7x Manual and from this full package download you can simply extract the current “d7x\d7x v18.3.17.1.exe” (or higher) to your existing d7x directory, making sure to remove any prior d7x vx.x.x.x.exe files before running this current version.

Also in the full package download you will find “d7x\d7x Resources\d7xRDT v18.3.17.1.exe” which can be placed in your existing directories (also removing the existing versions of that file) although you may save this step since the current d7x in that package will properly download this (if missing) when you are creating a new self-extracting d7xRDT for usage.

To create a new d7xRDT (which btw now self-updates when deployed remotely, and is also working I might add) from the main interface in d7x, click the Servers drop down menu at the top, then select Config Mgmt Portal, and use the button on the bottom to create a new d7xRDT.

What happened?

The issue stems from an expired SSL certificate (on Feb. 26th) and it was far more of an issue than previously thought (doh!)  New verifications are used by d7x to assure our server’s identity when establishing secure connections, and some additional checks reject the connection when the certificate is expired (even if the same cert is renewed.)  Although this specific requirement should have been removed in the last few releases, it wasn’t, therefore leaving the previous certificate in place until most or all application updates were made would not achieve a desired result.  Of course a new certificate is currently in use.

While these things happen from time to time, I personally couldn’t regret the issue any more than I already do.  I cannot overstate the additional care to be taken in the future with regard to the security and the update process.  For now, please accept a sincere apology for any inconvenience this may cause.

So what else is new with d7x?

d7x v18.3.17.1 has a lot of small fixes and features, and more complete list should soon make it to the d7x Manual, but here’s a few to inject some good news into this blog post.

  • New:  Technician Password correction prompts.  When extracting an encrypted config archive, d7x will prompt if the technician password (used for archive encryption) is incorrect, allowing the option to retry as many times as necessary.  Previously the extraction aborted/failed leaving a blank config, triggering the d7x registration prompt on launch.  This has actually been an issue since d7 Premium with dCloud, but rarely a problem since typically no one changes that password.  Also by having few options in d7/d7II/d7x that require it’s manual input, this is why it can easily be forgotten and not become an issue for quite some time.  It usually takes a new major release (d7II, and now d7x) when those opting for the “clean download/setup” can bring this on with new configs created using different technician passwords entered during the initial registration process.
  • Fixed:  Failure to run scripts within custom app configurations that used the %scriptdir% variable to point outside of the 3rd Party Tools directory.  Possibly other cases were an issue resulting from the bug.  Further, some custom apps were failing without a download URL being configured.
  • Fixed:  d7x sometimes failed to restart itself along with Windows.  Previous versions ran shutdown code which removed the startup entry responsible for launching d7x after a Windows restart; this also stalled auto mode operation until d7x was manually launched again.
  • Fixed web links opening in the d7x internal browser despite being configured to use the system default web browser.
  • Change:  The titlebar previously forced the version display, ignoring user preference (this is by design for TestBuild and FastTrack releases, but removed in FastTrack currently until the Release follows soon.)

 

So what else is new with d7xRDT?  (Remote Deployment Tool)

As stated previously, d7xRDT v18.3.17.1 will now self-update it’s own binary when deployed, ironically to ensure server connectivity with updates as changes are required.  This was actually introduced for similar issues in the past with the d7II “SFX Mini” (the previous gen d7xRDT.)

Along the same lines, soon the d7xRDT will download d7x binaries from your own http-based URL (similar to using self-hosted FTP for config/definitions storage) as well as ours, in case of connectivity issues.  In fact this version of the d7xRDT binary has the code in place as it was also planned prior to this incident, however a new d7x version will still be required to generate and embed the new self-hosted configuration inside the d7xRDT package which you will deploy with, as well as the appropriate d7x archive that you would host on your server.

Stay tuned for more…

]]>
https://www.d7xtech.com/2018/03/d7x-v18-3-16-0-and-above-are-required-for-future-updates-older-versions-will-not-recognize-update-availability/feed/ 1 14132
d7II to d7x update error corrected, please accept my personal apology for any disruption in usage! https://www.d7xtech.com/2017/10/d7ii-to-d7x-update-error-corrected-please-accept-my-personal-apology-for-any-disruption-in-usage/ Wed, 01 Nov 2017 02:35:25 +0000 http://www.foolishit.com/?p=13181 Please accept that I deeply regret any inconveniences you and others have experienced due to the upgrade failures.

A corrupted archive file (containing the final part of the update to the current d7x “FastTrack” release) was replaced on our servers this morning (around 12 hours ago) which resolved the issue in our testing (using the same copies of d7II on the same systems that consistently reproduced the behavior.)

To be clear, the issue resolved today on October 31st, 2017 at around 7AM or 8AM Eastern time zone (3-4AM UTC) is regarding the extraction failure occurring during the update from d7II to d7x, and leaving a d7II.exe file in the directory that may have the version 3.6.87 but that is reduced in size (about 1.2MB instead of the 6.9MB as would be a d7II v3.6.86 or actual newer v3.6.87 executable) and that smaller d7II.exe (an “update stub”) would give the same extraction failures consistently upon any subsequent relaunch.  This issue is now resolved in what is now extensive testing throughout today.  Relaunching the same d7II.exe file (around a 1.2MB file) should now (as of the time specified above) complete the update as expected, and run the newly extracted d7x executable.

 

During the failure, you may have noticed a few other files that were left in the d7II directory, one of which was d7II.exe.d7II_Exe_0 (or similar.)  Renaming the file to leave the first part of the filename “d7II.exe” (you can also think of as removing the temporary file extension) would leave you the previous v3.6.86 d7II.exe file, ready for full usage, as normal and expected.  Unfortunately, we must now regret that without instructions suddenly appearing in the d7II directory, this would not have been obvious to most users, and we realize a tech that is onsite, or out “in the field” might not have a second flash drive or a copy/backup/any other accessible means to recover and use d7II at that time.

While it didn’t help this time, currently d7x contains several update fail-safe mechanisms not in d7II, as well as new update prompts/information and textual instructions that can be delivered and saved in the d7x exe’s directory in plain text files prior to the update process, should something crazy ever occur again despite the fail-safe routines.  Unfortunately, the d7x capable of newer fail-safe behaviors is the very thing failing to extract from the corrupted download in this case (how embarrassing, but it does demonstrate the need for the new d7x code!)

 

Also, I feel like it is equally important to take this opportunity and make clear that the new d7x is a “FastTrack” build, and not all functionality may function as expected (although there should be few if any issues beyond “Offline” functionality and the minor issues in current documentation.)  Please always read about any current issues in the d7x manual.  FastTrack builds are like the “Pre-Release” updates in d7II, or think of the “Release Candidates” in similar Windows terminology of the recent past.)  For d7x, the FastTrack builds are intended to give techs a working copy of new d7x code to use and to provide us with feedback on any features or changes.

Once standard in d7II as “Pre-Release” updates, d7II no longer detects the cutting edge update type, which was disabled in the final releases before the d7II code freeze on new features during d7x Platform code development.  As a result, the early release of d7x was only possible via the mainstream d7II update.  Those who were not long-term subscribers of d7II or who may have updated without reading the information on our d7II -> d7x update announcement (linked to via the lower status bar of d7II) may not be aware of the meaning behind the “FastTrack” status reflected in d7x’s top title bar.

 

Please accept my personal apologies for any troubles incurred as a result of the recent update failure.  Also, please be aware of the d7x related links below, for your benefit now and in the future, and be sure to submit feedback on the product as your time permits, so we can ensure that d7x is the app you want and need it to be, and that we don’t miss anything as we strive to exceed your expectations!

——————————
Product Links:
——————————
d7x Release Information:  www.d7xtech.com/d7x/update
d7x Manual/Current Info:  www.d7xtech.com/d7x/manual
d7x Videos (Playlist):    www.d7xtech.com/d7x/youtube
d7x Product Page:         www.d7xtech.com/d7x

]]>
13181
d7x is officially updating for all d7II subscribers… https://www.d7xtech.com/2017/10/d7x-beta-is-officially-updating-for-all-d7ii-subscribers/ Tue, 24 Oct 2017 14:10:32 +0000 http://www.foolishit.com/?p=13060 d7II subscribers will notice their copy of d7II v3.6.86 (or earlier) now promotes that an update exists to v3.6.87 (there is no actual code change for this specific .exe version; the version number is incremented to silence d7II update notifications if used after this d7x release.)

d7x Release Information

d7x-med-256

[Some information may be outdated]  Please see the d7x Manual for ALL current product information and downloads.  

d7x is the name given to the successor of d7II, our current generation PC technician productivity software.  Initial incarnations of d7x combine the underlying d7x Platform code (developed separately from d7II itself) with the d7II interfaces and much of the specific functionality, to bring product updates to d7II subscribers as soon as possible (until a fully unique d7x release is achieved) while simultaneously moving towards that goal.  Therefore, an active d7II subscription is required for any testing or usage.  In fact, to have an active d7II subscription means you are a d7x subscriber, even if your billing plan doesn’t to change reflect the new name.

d7x is currently designed to sit beside d7II in the same folder, and maintains backwards compatibility with d7II configurations and active d7II session data (temporary files and settings specific to d7II and the current repair process) so a job can be finished with d7II if necessary.  Even if d7x stopped working during an auto mode, d7II should pick up where d7x left off.

We’re excited to once again invite any d7x (d7II) subscribers to actively participate in the feedback process for current development.  We hope to continue d7x in the d7 tradition where techs contribute insightful and experienced ideas for current needs, inspiring the program features that have made the d7 and d7II great from day one!  Contribute your ideas anytime by contacting us directly or via our official support portal where you will also find message forums capable of housing your discussions on feature requests and updates for all of our software!

What's Different

d7x Platform code controls the underlying operation of d7II specific functionality (from error handling/debug systems to interfacing with the OS, file system, registry, internet operations, and more…)

d7x interfaces with the OS using new APIs that allow newer OS features and replace older concepts and tools, while preserving Unicode characters with an aim to cover the different needs of those in non-English speaking countries and with localized versions of Windows.

d7x advances client/server communications adding full SSL and verifying server security certificates on connection, for secure update communications to safeguard against attacks.  These capabilities will be extended to the “dCloud” communications when accounts can be migrated/converted, and to Self-Hosted FTP options, as well as adding new HTTPS communication abilities for Self-Hosted options.

d7x also interfaces with itself using high accuracy and error correcting routines in certain input data verification code, and includes vastly improved error handling and debug systems that automatically track quite a bit of internal data flow without extra coding.

The initially availability of “d7IIx” (named to reflect a hybrid product) earlier this year began with d7x “Platform” code, built from the ground up with new considerations in design and new fundamental basic lower-level functionality, and integrated the d7II user interface and other code designed for specific purposes and functionality (e.g. specific Windows repair processes, the entire custom apps system, etc.)  Then, much of the d7II code was unmodified, although certain things reflected improvement right away (such as Windows 10 recognition.)  Now, d7II code and specific functionality is being replaced entirely in areas like config/definitions storage operations and remote deployment options, and more is to come.

The d7x Platform code is designed not only for innovations not possible with d7II code, but also to provide a more flexible platform to be used for rapid development (and updating) of multiple application projects going forward (including our other existing technician oriented apps such as KillEmAll, dUninstaller, and dSupportSuite to name a few, as well as other new apps on the horizon.)  In fact, d7x Platform code powers the CryptoPrevent v8.x “Program Filter” module, an invisible component enabling features based on the real-time hash signature and logic-based filtering of executable files at run-time.

Specific Examples of Code Integration

To get a better idea of how the d7II code fits in, below are a few examples which illustrate the relationship between new d7x Platform code [represented by (d7x) below] which performs the unseen “grunt work” vs. the ported d7II code [represented by (d7II) below] which still handles the interface and specific/customized functionality.

Current Example #1:  Run a custom app from the user interface (d7II), read user config (d7II), determine applicable operating environment/OS version (d7x), file exist/date stamp checking to determine if we should download a new fresh copy (d7x), download the file (d7x), extract file (d7x), find/verify extracted files (d7x), determine/initiate config customizations to app (d7II), perform file/registry operations related to app customizations (d7x), launch executable (d7x), wait for it to complete (d7x) in order to perform any cleanup/post actions like log gathering, etc. (d7II) before continuing with auto mode if in progress (d7II).

Current Example #2:  Launch a Windows repair function from the user interface (d7II), read user config if applicable (d7II), determine targeted repair methodologies for the specific circumstances based on the above (d7II), determine operating conditions/perform system checks/download reqs if applicable (d7x), actually perform targeted repairs via any number of file system/registry operations (d7x), report success/failure/subsequent actions determined (d7II).

Now that the d7x Platform code has been integrated fully with the last builds going by the “d7IIx” title, much of the existing d7II specific code (as mentioned above) is being replaced, and fast.  The current d7x v0.0.0.88 update brought an entirely new Config Mgmt Portal (older dCloud/Self-Hosted FTP functionality) and introduces the d7x Remote Deployment Tool (aka d7xRDT, the ‘SFX Mini‘ replacement) both of which are all new d7x specific/d7x Platform code (d7x-only) and together replace ALL client/server communications regarding config/definition files, as well as update tracking functionality.

Current Development Focus

Our first and foremost priority is to document/fix any remaining issues with functionality that worked correctly in the last release version of d7II.

New Feature Suggestions:  At this time we are open to new feature suggestions, and large ideas are welcome; please visit our support portal to start a community post, but we ask that you understand the consideration is in future implementation, and we may not address all requests.

For the near future:  major sections of d7x Platform code are already established (in the binary) and waiting to be integrated into existing d7II code replacements.  The new d7x Platform code focuses on advanced, tested, stable, and reusable code to allow for rapid development towards reconstructing many of d7II’s best attributes into a more powerful and more user friendly tool.

Focusing on stability in the integration of d7II specific interfaces and functionality, workflow and data formats must be re-designed before we can drop d7II operational compatibility, and we plan to drop d7II operational compatibility before we move on to newer possibilities and new features.

User Interface:  There is no foreseeable ETA on a complete user interface “change” at this time.  In valuing function over form, for the most part your familiar interface will change gradually when it isn’t optional, and optional when it isn’t gradual or “under the hood” and does not maintain a familiar d7II form.  Currently there may be few UI elements that reflect interface changes conceived for d7x, however there is a lot of re-usable code ready for interface changes or more simple enhancements.

Those hoping for few major “graphical” changes (if any) may delight in seeing the new KillEmAll’s background, which forces a consistent appearance of mostly the same traditional Windows app background color across all versions of Windows, while adding only a slight gradient effect from top to bottom using a bitmap that resizes nicely.  It’s worth noting that this bitmap could be replaced as a new brand-able property.

Compatibility issues must also be considered as we apply new interface concepts, not just in maintaining d7II compatibility during the early stages, but also to allow the optional usage of the current d7II interface as a new UI develops, because a large amount of specific d7II functionality is tightly integrated into the existing user interface.  In order to replace the d7II user interface that code must be updated heavily or entirely rewritten to work with new d7x code, and to simultaneously continue to work as expected with the existing d7II interface.

In other words, d7x is a ground up replacement, and basically the UI is more or less a major part of the very final stages in a full d7x release, but we’re not quite there yet.

d7x Release Timeline

October 2017:  d7x has been rolled out to d7II subscribers!

d7x initial rollout; d7II subscribers will notice their copy of d7II v3.6.86 (or earlier) promotes an update to v3.6.87 (there is no actual code change for this specific .exe version; the version number is incremented to silence d7II update notifications if used after this d7x release.)

  • Download d7II.exe for use as a backup (if missing) using the d7x “Main” menu > “Check for Updates” option.  (This should be done automatically when updating from d7II.exe)
  • NOTE:  Offline tab functionality is NOT fully functional in this d7x 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.)

 

September 2017:  The latest d7x TestBuild replaced the d7IIx Alpha versions, which could be tested with confidence in a production environment (provided you kept d7II with you as a backup.)

March 2017:  d7IIx was released to early adopting d7II subscribers for assistance in testing.

Earlier:  d7II specific code was merged with a mostly completed d7x Platform based code project (being ready to adopt specific d7II functionality) under the name “d7IIx Alpha” for a time.

Where to Download / What to Expect

(Current availability) d7x has been released to all d7II subscribers through the standard in-app update system.  If you are not yet prompted to update, visit the Main menu (top left) > Check for Updates from within d7II.

Alternately, you can get blank-config product downloads from the d7x Manual, or pre-configured product downloads from dMZ Additional Downloads page (requires your “uid-” dMZ login.)  Both require supplying either your d7II/d7x registration information and account credentials, or the Reg.Settings.dat file from a d7II\Config directory containing a registered/working copy of d7II.

After the d7x update, d7II.exe can still be used on the same PC, and within the same session.  This is intended as a fail-safe option, in the event of any unexpected d7x crash or functional failure.

In order to facilitate the d7II fail-safe functionality, d7II is the “dominate” app, and will assume any active d7x session data yet replace the original path/.exe file in the registry with itself for future use.

Additionally, d7x will not start if an active d7II process is found, or if d7II is launched first without using End Session (except when d7x is launched during the update process.)  In order to switch back to using d7x on that system, you must use the End Session functionality in d7II, or modify/delete the appropriate d7II session data.

Detail:  d7x determines the location of the d7II path/.exe from values found in the “HKLM\Software\Foolish IT\d7II\Session\Paths” key.  If the .exe file exists, it will launch that .exe (passing any command line arguments that were received by this d7x process instance) then terminate itself as the d7II process starts up using the rest of the d7II session data created by d7x for backwards compatibility.

d7x-d7II session behavior may be phased out or triggered by user prompt as features are added to d7x which become necessary for the desired behavior, yet have no backwards compatible equivalent for d7II, causing incomplete (and possibly unknown) behavior with d7II.

Please see the d7x Manual for ALL current product information and downloads.  

 

d7x FAQ  

Q: I have d7II. Will I need to purchase a new or upgraded license?
A:  NO!  New name, new logo, same license/subscription!  ALL existing licensed copies of d7II will automatically update to d7IIx/d7x at their respective release dates, while incurring no additional charges of any type, at any time.  The d7IIx and d7x upgrades are naturally a part of your existing d7II license, including “lifetime” licenses.  Basically, if you have a licensed and working copy of d7II, you are included!

In fact, to have an active d7II subscription means you are now considered a d7x subscriber, and will be referred to as such in future documentation and emails.  Note that some billing related emails may not reflect the new name, nor will Paypal accounts/emails when used for recurring subscription payments.

Q: I have d7II. Will I need to reconfigure it after the update?
A:  Only a little, but we’re aiming to deliver a ‘painless’ experience!  Some configuration may be necessary for new or updated functionality, however d7x will upgrade anything relevant from an existing d7II configuration to the new d7x format automatically.  If necessary, you will be prompted during conversion with a central interface to aggregate the changes and assist you in making any decisions about any new settings which may be necessary.

Change may be required:

All copies of a “d7II SFX Mini” used in remote deployment will continue to download only the last versions of d7II.  If configured, d7II could automatically update to d7x with every usage adding considerable time to the initial startup from the SFX Mini, as well as allowing for potential complications (currently the d7II-d7x update process involves 5-7 separate downloads through an updater stub, and would occur after the SFX Mini downloads all d7II components that will be disregarded by d7x.)

  • To continue using d7II and the SFX Mini, you should ensure any d7II config(s) used with your SFX Mini have disabled automatic updating of the d7II application from the Config > Behavior tab, in the lower right column.  Save and upload any config back to the cloud (or your self-hosted FTP) if the d7II automatic update option was enabled for session or app startup.
  • For a d7x replacement to the SFX Mini, (which will download d7x instead of d7II) you must create and use the newer d7xRDT (Remote Deployment Tool) – details are in the d7x Manual.
Q: Will there be a price change?
A:  YES for NEW subscriptions (this includes REACTIVATED d7II accounts!)  [not yet implemented]  As d7x becomes available there will be pricing adjustment of some measure, but for new subscriptions only.  A new “subscription” refers to the subscription billing agreement/payment schedule, NOT the d7II owner account, therefore ALL previously cancelled/invalidated/lapsed d7II subscriptions have already lost the originally associated pricing rate, and any former subscriber who wishes resubscribe must do so under the current pricing rates available to new subscribers.

A:  NO for currently active d7II accounts!  Customer loyalty deserves reward, so ALL existing d7II accounts which remain active are eligible for d7x based upgrades with NO change in your existing pricing terms.  Actively billed subscription plans will continue to be charged at the previously agreed upon rate (as determined when you committed to that payment plan through our 3rd party payment processor) provided that your subscription is maintained without a lapse in payment or service.

* Please note that d7II is licensed at per-technician rates (single tech, 2-5 techs, 6-10, 11-15, etc.) and therefore to increase technician usage at any time would require a new/upgraded license, which does constitute a new subscription plan that may be charged at the current rates.  Additionally, any d7II account cancellation (prompted either by customer request, or due to a lapse in payment/subscription without a timely customer response to rectify the missed payment and reinstate service) will require a new subscription to be charged at the current rate for the product during that time.

Q: Will there be a free edition, trial period, or a one-time purchase option?
A:  We are considering a limited free edition possibly with full version trial capabilities, as well as a one-time purchase option for certain modular areas of d7x functionality.  These are low priority considerations and entirely dependent on finding a good functional balance in separation of features, with respect to what we have (or have not) planned for future functionality in the ever-evolving full edition.
Q: What does the 'x' stand for, 10 or something?

A:  NO!  To be honest, some of us believe the usage of the letter ‘X’ in pop culture is a bit annoying, so our ‘x’ actually gets its inspiration from a common convention in programming (and math formulas) to use ‘x’ as the primary variable name.  In programming a variable can be substituted with a real value in repetitious code blocks, with ‘x’ often used as the numerical index in For…Next loop statements e.g. For x = 0 to Ubound(SomeArray)…  ‘x’ is also the most recognized way to refer to multiple or unknown specific software versions, like referring to a range of revisions at once, e.g. v4.x instead of v4.0 and v4.1 and v4.2, etc.

Either way you look at it, d7x represents a variable:  it is ever-evolving and improving to suit the expanding needs of PC repair technicians everywhere!

 

]]>
13060
d7x (Alpha) September Update (Updated) https://www.d7xtech.com/2017/09/d7x-alpha-september-update-updated/ Fri, 22 Sep 2017 22:07:10 +0000 http://www.foolishit.com/?p=12988 d7x v0.0.0.90 just released 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.

Although we’re not looking to add new features in d7x Alpha at the moment until we have tested everything, had good feedback from testers, and are confident in bringing this to the d7II “Pre-Release” stage, there are *minor* improvements we’d like to make along the way.

This is a great example of what these look like.  So if you have any suggestions that will add some real use to d7x right now, let us know.  While we can’t guarantee anything no matter how small at the moment, we would like to see what the current ideas are shaping up to look like as we begin to wrap up some things and proceed to new areas in d7II code replacement.

See this post if you missed it, and/or need any links:

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 to all d7II subscribers in March.   We believe this release can be tested with confidence in a production environment, provided you keep d7II with you as a backup.  d7x Alpha is designed to sit beside d7II in the same folder, and maintains backwards compatibility with […]

 

]]>
12988
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! https://www.d7xtech.com/2017/09/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/ Thu, 21 Sep 2017 19:15:58 +0000 http://www.foolishit.com/?p=12919 This latest d7x Alpha “TestBuild” replaces the “d7IIx Alpha” versions opened to all d7II subscribers in March.  

We believe this release can be tested with confidence in a production environment, provided you keep d7II with you as a backup.  d7x Alpha is designed to sit beside d7II in the same folder, and maintains backwards compatibility with d7II configurations and active d7II session data (temporary files and settings specific to d7II and the current repair process) so a job can be finished with d7II if necessary.  Even if d7x stopped working during an auto mode, d7II should pick up where d7x left off.

The next release stage will bring the d7x “FastTrack” builds to the d7II “Pre-Release” update system, and later as a full next-version release through the standard automatic update system.

Please see the d7x Manual to download and learn more about what’s new with this release, including the d7x Remote Deployment Tool (aka d7xRDT) the “SFX Mini” replacement, and new Config Mgmt Portal replacing the dCloud/Self-Hosted FTP functionality.

Also, this d7x Alpha Youtube playlist was created for early demo and how-to content, and currently contains a new video on the d7x Bug Submission Interface, but 2 more videos with new content are already awaiting edit.  (Be sure to subscribe to our channel for update notifications!)

Tuesday’s Foolish Tech Show also has a rough/impromptu and fairly long overview of some new functionality, which we go over after the whole CCleaner fiasco.

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.

 

]]>
12919
CCleaner (Piriform) Malicious Code Breach! d7x/d7II/dSupportSuite Users Take Notice! https://www.d7xtech.com/2017/09/ccleaner-piriform-malicious-code-breach-d7xd7iidsupportsuite-users-take-notice/ https://www.d7xtech.com/2017/09/ccleaner-piriform-malicious-code-breach-d7xd7iidsupportsuite-users-take-notice/#comments Wed, 20 Sep 2017 14:51:01 +0000 http://www.foolishit.com/?p=12907 Sept 26th, 2017 Update:  Yesterday this appeared on Bleeping Computer:

Avast Publishes Full List of Companies Affected by CCleaner Second-Stage Malware
https://www.bleepingcomputer.com/news/security/avast-publishes-full-list-of-companies-affected-by-ccleaner-second-stage-malware/

Bleeping also put out a nice article from the 22nd, containing a nice summary if you’re just catching up on the news (because of course more has emerged since our last update, and we shouldn’t just assume you read it elsewhere):  

Info on CCleaner Infections Lost Due To Malware Server Running Out of Disk Space
https://www.bleepingcomputer.com/news/security/info-on-ccleaner-infections-lost-due-to-malware-server-running-out-of-disk-space/


Sept 21st, 2017 Update:  These articles also came out yesterday, unfolding some plot twists to this story.  If you get your news here, you could do better!  

It seems a new backdoor was discovered and … you just need to read these:

CCleaner Command and Control Causes Concern
http://blog.talosintelligence.com/2017/09/ccleaner-c2-concern.html

CCleaner Malware Infects Big Tech Companies With Second Backdoor
http://thehackernews.com/2017/09/ccleaner-malware-hacking.html

Original post is below, but be aware some details may no longer be accurate as the story unfolds.


This came out two days ago on the CCleaner blog:  Security Notification for CCleaner v5.33.6162 and CCleaner Cloud v1.07.3191 for 32-bit Windows users.

It seems that CCleaner has had malicious code bundled into their 32bit binaries (along with their “Cloud” version) and the tampering occurred prior to distribution.  The infected binaries were provided for download from their official site/update servers and distributed legitimately for about a month, silently infecting users to send data back to the ethers.  It also occurred completely under the nose of their new parent company Avast, the anti-virus software maker who acquired Piriform (the makers of CCleaner) as recently as July.  In fact, yesterday Avast released their own blog post about it, Update to the CCleaner 5.33.6162 Security Incident.

For the consumers who’ve used any of their products, you need to know this, but I’ve got ZERO advice for what you do with that information (other than maybe call a tech if you aren’t tech oriented, because you have software on your PC that is sending bits of your data elsewhere.)  On second thought, I’m told that Malwarebytes says their software removes/fixes it, and I see they have a blog post here:  [Updated] Infected CCleaner downloads from official servers (they have the free/trial/paid user-level “scanner” software which I’m sure all editions take care of the issue quite effectively.)

With prevention, the damage is done and over for the most part unless you’re still running the infected CCleaner, but that person isn’t reading this article…  By next update at least all of our CryptoPrevent users who haven’t noticed or heard should have detection sigs for the affected binaries, and Folder Watch can quarantine or the Program Filtering can pick it up on execution as well.  In fact from a few days ago when ClamAV was the only anti-virus engine to detect it (VirusTotal.com) today it lists 41/64 engines detecting it, and that’s just how it goes in this industry.  If you have the infection but you have any sort of security software, you won’t have the infection for long.

Finally the elephant in the room is trust.

I’m sure that the CCleaner developer could’ve been as shocked as anyone else to learn about the incident, but I just don’t know.  As for Avast, if checking CCleaner (and their other software) binaries with their own security staff, or even just a little software scan with their product, was not part of their decision to acquire Piriform/CCleaner, then I’d be very surprised (and maybe I should be…)

Regardless, if you use CCleaner or Piriform products, I don’t think that this is any reason to stop using them, or the parent company’s Avast’s products.  We should all now agree that malicious activity can breach even the most trustworthy, and we should also agree that when the incident is over it isn’t always a “trust” issue at all, maybe it’s more rare than we’d normally admit, but we just got burned.  So far that’s all anyone knows here, but the thing is it wasn’t just CCleaner users, but the people at Piriform got burned too, meaning whoever punches the clock there that isn’t involved in this (which is up to and including maybe everyone.)

I have no real advice here, and in fact I would like to explicitly offer no suggestion at all; but at this point in time, there are two points to understand:

1.  Piriform hasn’t entirely dealt with the issue until they know who did it, but that is a legitimate and long established “good” app and company, and you should have no doubt that Piriform (and their parent company Avast, the makers of that big anti-virus software product, I might reiterate) will be paying attention more closely from here on out.  That should be more comforting than it might sound to someone already burned.

2.  Realize that this can happen to any other legitimate and long established (“trusted”) software by the time you make the switch, if it didn’t happen already and it’s just undetected to date (as was the case here.)  

So the best I can offer for the time being is just a little food for your own thought, with the disclaimer that you take this information like anything else you read on the internets, with a grain of salt!  (That, and don’t forget you are likely infected, so get your PC looked at!)  

 

Now, speaking only to our IT Professional / Tech Shop customers, here’s what you need to know as a tech/IT pro who maybe uses CCleaner through a custom app profile with our software:

Malicious code has infected 32bit binaries of the 3rd party software CCleaner, which can be found as a default/included custom app profile in our more popular tech-oriented/non-consumer Foolish IT apps dating back to the original d7, so there’s a high probability that someone is using it in their tech work and repair scenarios…  64bit systems are unaffected, and there isn’t a “Cloud” version in our example profiles for 3rd party applications, so you should know if that’s an issue because you created and use the customized profile.

It’s worthy of note the malicious code was planted … ok I haven’t read it all (it would seem at least before digital code signing) which means it was an “inside job” and therefore changing your download links in the custom app profiles won’t matter, it wasn’t that kind of breach…

For more technicals on the CCleaner thing, the folks at Cisco’s Talos Intelligence Group have a nice technical analysis in CCleanup: A Vast Number of Machines at Risk and thanks to our own Brantley for the link, who pointed out the pic of ClamAV near the bottom with the very first detection, good job!  (ClamAV is an anti-virus engine which seems like the historical last to recognize or do much of anything, another fine example of how things shift quickly, frequently, and wildly in this industry.)

 

d7II and d7x (Alpha)

CCleaner (under the default custom app in d7II/d7x) should re-download itself every 7 days, so if the affected version exists in your d7II 3rd Party Tools directory, and for example you lived under a rock and didn’t know about the breach, then the infected version will be there for at most another 5 days before it is replaced by Piriform’s most recent version which we would all hope is still as clean as it should be right now.

In fact, you can disable the re-download option right now (d7II Config for the custom app, persistent settings tab, you want the check at the top I believe) and it won’t ever update unless it isn’t there, so in a bench / network / office / USB flash drive scenario you’re good to go with the download you have, still a very good program for what it does and more than likely legit/clean at the moment, and it won’t update anymore so you can use it without worrying about the profile updating it to a version you don’t trust yet.

Of course you’re reading this, and hopefully you clicked on the alert in the lower status bar, then please just go delete the entire “\3rd Party Tools\ccleaner” directory, and the “\3rd Party Tools\ccleaner.zip” file if they exist from ALL of your copies of d7II/d7x, and be done with it; the (hopefully) still clean versions will download automatically as usual, as you decide to use them.

If you made it this far and you are a d7II subscriber, please also check out the d7x Alpha info page to understand what is different and consider testing it, the download is found in the new d7x Manual.

 

d7 (original/free)

I do believe it is a default option for maintenance, and although I don’t recall the specific download rules in the final v10.something, I do not believe it updates much.  Anyone using this tool should seek to do the same as mentioned above and delete your CCleaner files, let them re-download and use that if you insist, for the time being.  Then look into d7II and the upcoming d7x first and step up.

 

dSupportSuite (and dMaintenance)

Owners of dSupportSuite may know the software includes example custom app profiles for CCleaner/Defraggler as 3rd party downloads, and those who’ve deployed dSS profiles to your clients using these apps are of course affected.

So with every maintenance cycle of dSupportSuite (weekly) by default when an internet connection exists it should attempt to download the latest 3rd party tools configured for use.  Good for the fix, not so much when it was a problem!  The same automated re-download on every maintenance also applies to the older dMaintenance stand-alone apps (both the original tech version and later home edition.)

Although the issue has been corrected (for the moment) on Piriform’s end, and we’re sure that they (and their parent company alike) will be keeping a close eye on future releases, you wouldn’t be wrong to push out a new profile that doesn’t include it, at least for a time.

Also, those machines have infected code possibly running on them right now, and as much as any fix (which will more than likely be present in their security product already on their system within the next few days, if it isn’t already neutralized) your clients need to be made aware of the breach itself.

 

The same goes for many tech shops and repair guys out there, I think your customers need to hear it IF they can possibly be affected.  Probably most tech shops at one point in time or another have had at least one employee use CCleaner on a customer’s system, quite a few probably within the last month, world-wide…  That’s conservative, but my guess more than likely is that CCleaner is just part of the way things are done in many tech shops, by most if not all techs who are allowed to do their own thing, if not being some semi-to-official company mandate (depending on how large the company is they shy away from 3rd party apps without $$ agreements, but under 20 employees it’s completely possible.)  It surely is in the toolbox of most door to door guys, wouldn’t you think?

This wide-spread usage is for a good reason, let’s not forget.  I think most agree it’s also good at doing what it advertises.  Dispute the app’s necessity all you want (and I would personally do it in some other article to some degree) but I don’t ever recall finding fault with the company’s character, and we still have it in the custom app profiles our tech customers use for a reason.  As stated earlier it is a legitimate and long established “good” app and company, so don’t’ forget Piriform’s reputation and read up on how they are handling it well right now.

I’m sure since it’s so widely respected and used, a quick visit to your favorite tech forums and you’ll find plenty of tips and example scripts on what others are already saying to their customers.

I know it’s an ugly conversation with any client, depending on how one might view the situation, but if you approach it with honesty, it can be a good opportunity to reconnect with clients maybe you haven’t seen in a while, and show them some concern and care.  It’s good to build any of your client relationships through all seasons, and the integrity pays in good ways.

 

]]>
https://www.d7xtech.com/2017/09/ccleaner-piriform-malicious-code-breach-d7xd7iidsupportsuite-users-take-notice/feed/ 1 12907