Command line stopped working after update to update 4
After a recent update to update 4, I immediately noticed that command line and powershell began crashing when trying to launch. This is the second time that it has happened each time after installing the update to Acronis. Not sure if it is related to the update or if it is my machine.
Has anyone else experienced this or is it just me?
Steve,
Thank you for the response.
My exact use case is as follows
For Command Line:
- Press Windows + R (Open the run command)
- type cmd
This will launch the window for a split second and then it immediately closes.
Similar for Powershell
- Right click on the start button
- Execute Powershell or Powershell as Admin
This will launch the window and immediately closes.
In both cases nothing is reported in event viewer.
I normally notice it because Visual Studio stops compiling applications as it utilizes command line to compile applications.
As for the upgrade path, I normally just click the "Download" button on the "New Update Available" window.
Applications that are generally running while this is taking place (I don't recall the first time it happened) however; I know Visual Studio was open as well as Trend Micro Antivirus running in the background in both instances.
The first time this happened I had installed multiple items that day:
- WSL2
- Ubuntu Kernel for Windows
- Docker
- Acronis True Image (Update 4)
I originally thought it was Docker or its requirements, so I had held off on installing it again; however, it happened again after I installed Acronis True Image once more a couple days ago.
As far as system configuration:
I am running Windows 10 Pro
16 GB Ram
1TB SSD
Rick, thanks for the clarification - this is certainly very strange and not an issue that I have seen reported by any other users in the forums, nor experienced myself.
My first suggestion would be to turn off all the new Protection features in the ATI 2021 GUI by opening the Protection tab. If this makes a difference, then it would suggest that something in the protection feature is blocking the command / powershell launch!
As you say you have already uninstalled / reinstalled ATI 2021 build 39184, if the problem continues, then I would recommend raising this direct with Acronis Support by opening a support case with them.
Thank you for the suggestion
I will try that a little later, I have actually done a system restore to rollback to the previous working state. So I am back on build 35860. When I have a chance, I will try disabling the protection system. I might turn off Trend Micro during the update as well. After losing two full development days the company I work for is not to keen on me trying to do this again. It might be a weekend project or something.
A bit of troubleshooting advice here.
If you choose to attempt to update to release 4 again, close all open apps prior to running the update. After the update is complete, do not start the ATI application. Instead close the installer, go to the Windows Power options and select restart. Once restarted see if the problem still exists.
If the problem still exists perform a Clean Boot (google it) and then check to see if PS and command prompt are working properly. If they are then that suggest the issue was introduced by the ATI update.
Have the same issue (have Acronis 2021 & run trend wfbs)..so far cmd and powershell will only run with Trend turned off.
IS there a way to turn off the Acronis 'protection' parts?
Cross reference to topic: True Image 2021 39184 breaks qBitTorrent 4.3.3 using Python 3.9.2 - where Bruce also reports issues with CMD & Powershell.
Note: Trend security apps in common? Trend Micro Maximum Security listed for Bruce from the msinfo32 report of Program Groups. Trend Micro Antivirus referenced in Rick's topic.
Steve Smith wrote:Cross reference to topic: True Image 2021 39184 breaks qBitTorrent 4.3.3 using Python 3.9.2 - where Bruce also reports issues with CMD & Powershell.
Note: Trend security apps in common? Trend Micro Maximum Security listed for Bruce from the msinfo32 report of Program Groups. Trend Micro Antivirus referenced in Rick's topic.
Bingo. Not just me. I have already tried disabling Trend Micro which didn't help so now I'll try uninstalling it.
Please let me know if you have success, I have not had a chance to troubleshoot any further.
I started with with 39184 installed and cmd.exe not working. I confirmed that just disabling Trend Micro Maximum Security does not fix cmd. It does not.
I uninstalled TMMS and cmd.exe now works.
I was curious if TMMS was affecting the installation of 39184 so without TMMS installed, I uninstalled and reinstalled 39184 and cmd.exe kept working.
I reinstalled TMMS and after rebooting cmd.exe started failing again.
39184 is doing something TMMS doesn't like, even when TMMS is disabled.
Rick, thanks for posting the trouble you're having. From the beginning, with cmd.exe and powershell.exe being the only exe's being attacked, this has smelled like something a virus might do to make it harder to remove the virus.
39184 is already under fire for not completely shutting off Active Protection even when disabled. Now it looks like TMMS might be guilty of the same thing, but that's a separate issue that made troubleshooting this harder.
It remains to be seen if 39184 really is acting like a virus or TMMS is too hypersensitive.
Anyway, clearly 39184 and TMMS are not playing nice with each other, even when TI Active Protection and TMMS are both disabled.
And thanks to Steve for his help too!
I found a kludge to make TMMS ignore cmd.exe powershell.exe. Those 2 files can be added to TMMS's Exception List.(Settings -> Exception List -> Program/Folders:
C:\Windows\System32\cmd.exe and C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
This is NOT a long term workaround as these 2 files are common targets for viruses.
Unfortunately this hasn't been helpful in getting qbittorrent working right.
Bruce.
Bruce, Rick, if you don't already have an open Support Case each for this issue, then I would strongly encourage you to raise one, and point support at both these forum topics.
In addition, you are welcome to reference support case 04838315 that I have open to complain about the constant logging and scanning / updating that is being performed by Acronis Protection services when they supposedly are 'turned off permanently'!