This project has moved and is read-only. For the latest updates, please go here.
6
Vote

VeraCrypt hangs the taskbar while dismounting a drive in Windows 10 64-bit

description

When I dismount a drive, VeraCrypt hangs the taskbar and after five minutes, the task bar unfreezes, and a notification appears, saying that the volume is dismounted.

comments

wmbruckner wrote Dec 8, 2016 at 9:05 AM

Same with me, cannot pin th issue on other software, happens after fresh install of Win10 Pro 64bit also.

wmbruckner wrote Dec 8, 2016 at 11:34 AM

adding to the aforementioned, on the same PC veracrypt runs without any problems on Ubuntu 16.04.

jbroen wrote Dec 20, 2016 at 9:29 PM

I have been experiencing the same symptoms using encrypted containers recently.
The problem first occurred after I exchange most of the hardware on my system (Only the HDDs remain the same.) VeraCrypt ran stable under OS Windows 10 64-bit on my previous system for several months before.

wmbruckner wrote Jan 12 at 7:29 AM

Interesting discovery: this behaviour only occurs when dismounting via context menu from the taskbar.

When I dismount the volune in the regular veracrypt window, it dismounts instantly and the taskbar is working just fine.

Hope that helps...

magic144 wrote Jan 20 at 7:11 PM

I see the same as wmbruckner's last comment - I can dismount without issue from the VeraCrypt app window, but if I dismount from the taskbar context, I get the hanging behavior. For me the explorer hang is about 2-3 minutes.

W10 x64 Home. Fully up-to-date. VeraCrypt 1.19.

ceroni wrote Jan 25 at 4:29 PM

I'm too experiencing exactly the same problem in one of my computers when dismounting an external Toshiba Canvio 1TB (MK1059GSM), entire hard disk encrypted with AES:
  • Veracrypt 1.19
  • Win10 Pro 64 (1607, build 14393.693)
  • Kaspersky Internet Security 17.0.0.611
  • Motherboard Asus Z170M-Plus, 32 GB DDR4-2400 MHz SDRAM, Core I7-6700
Interestingly, this problem does not occur when dismounting the same external HD on another computer:
Veracrypt 1.19
  • Win10 Pro 64 (1607, build 14393.693)
  • Windows Defender 4.10.14393.0
  • Motherboard Intel DH61CR, 8 GB DDR3-1333 MHz SDRAM, Core i5-2310

ceroni wrote Jan 25 at 11:58 PM

Confirming what has been reported: no issues when dismounting from the VeraCrypt app window; hangs 2-3 min when dismounting from the taskbar context.

Just did a quick test: disabling notifications from VeraCrypt in Win10 (Configuration>System>Notification & actions) cures the symptoms and was able to dismount from taskbar context without issues.

wmbruckner wrote Jan 26 at 7:39 AM

That works for me, too. Disabling notifications solves the issue. Thanks a lot, ceroni.

ceroni wrote Jan 27 at 12:41 PM

In my far from expert opinion this would point out to some "communication" problem between VeraCrypt and the Win10 notification system. However, one of the computers I use doesn't have the issue and runs exactly the same Win10 build the other machine presenting the issue.

magic144 wrote Jan 27 at 5:21 PM

I too have implemented the disable notifications workaround. Works for me. Thanks and credit to ceroni.

Hopefully the Notification mechanism glitch will be assigned and fixed in a later release.

ceroni wrote Jan 30 at 12:01 AM

Just experienced another lock up in the taskbar related to the Windows notification system. This time the culprit was a backup program I use (SecondCopy). Apparently it tried to inform about some skipped files and the taskbar hang for more than 5 min.
I'm quite sure this never happened in Win10 1511.

ceroni wrote Jan 30 at 2:02 PM

Googling around I've came across a suggestion that disabling Cortana through the group policy editor could solve the general taskbar hang problem.
Just tried it and the answer is NO.

ceroni wrote Feb 9 at 8:45 PM

Back to report my latest finds that could be helpful to others.
I’ve been trying to get rid of some persistent errors in the Windows’ logs and succeeded with all but 3:
  • DistributedCOM - EventID 10016
  • DistributedCOM - EventID 10010
  • Service Control Manager (Connected Devices Platform Service) - EventID 7023
Apparently the first one is easily fixed (see here – haven’t tried it myself yet).

However, I could not find in the forums a clear solution to the other two errors.
Today while doing some backups to an external hard disk using the program I’ve mentioned before (SecondCopy) I forgot to connect the drive and obviously there were errors. SecondCopy tried to report through the notification area the 6 failed backups and a very long taskbar lock up did occur. When I checked the error logs there were plenty of 10010 and 7023 events. Then I intentionally ran SecondCopy again at a specific time without the drive being connect and checked the logs:
09/02/2017 10:50:19
Service Control Manager 7023    "The Connected Devices Platform Service service terminated with the following error: Unspecified error"
09/02/2017 10:52:19
Microsoft-Windows-DistributedCOM    10010   The server {37998346-3765-45B1-8C66-AA88CA6B20B8} did not register with DCOM within the required timeout.

09/02/2017 10:52:19
Service Control Manager 7023    "The Connected Devices Platform Service service terminated with the following error: Unspecified error"
09/02/2017 10:54:19
Microsoft-Windows-DistributedCOM    10010   The server {37998346-3765-45B1-8C66-AA88CA6B20B8} did not register with DCOM within the required timeout.

09/02/2017 10:54:19
Service Control Manager 7023    "The Connected Devices Platform Service service terminated with the following error: Unspecified error"
09/02/2017 10:56:19
Microsoft-Windows-DistributedCOM    10010   The server {37998346-3765-45B1-8C66-AA88CA6B20B8} did not register with DCOM within the required timeout.

09/02/2017 10:56:19
Service Control Manager 7023    "The Connected Devices Platform Service service terminated with the following error: Unspecified error"
09/02/2017 10:58:19
Microsoft-Windows-DistributedCOM    10010   The server {37998346-3765-45B1-8C66-AA88CA6B20B8} did not register with DCOM within the required timeout.

09/02/2017 10:58:19
Service Control Manager 7023    "The Connected Devices Platform Service service terminated with the following error: Unspecified error"
09/02/2017 11:00:19
Microsoft-Windows-DistributedCOM    10010   The server {37998346-3765-45B1-8C66-AA88CA6B20B8} did not register with DCOM within the required timeout.

09/02/2017 11:00:27
Service Control Manager 7023    "The Connected Devices Platform Service service terminated with the following error: Unspecified error"
09/02/2017 11:02:27
Microsoft-Windows-DistributedCOM    10010   The server {37998346-3765-45B1-8C66-AA88CA6B20B8} did not register with DCOM within the required timeout.
There is a pair of 7023/10010 events with a 2 min gap between them for each error message issued.
The next obvious thing to do was to enable VeraCrypt notifications and check the error logs:
09/02/2017 13:03:01
Service Control Manager 7023    "The Connected Devices Platform Service service terminated with the following error: Unspecified error"
09/02/2017 13:05:01
Microsoft-Windows-DistributedCOM    10010   The server {37998346-3765-45B1-8C66-AA88CA6B20B8} did not register with DCOM within the required timeout.
Bingo, the same event pairs related to notifications with an exact 2 min gap.

Googling around for the “Connected Devices Platform Service” I’ve came across some suggestions that this service could be disabled without any visible impact on the system (see here).

It's been 5 h since I’ve disabled it and got rid of the notification problems.
Error logs clean.

ceroni wrote Mar 1 at 12:45 AM

Announcing Windows 10 Insider Preview Build 15046 for PC
Other changes, improvements, and fixes for PC
  • We fixed the issue causing Microsoft Edge and / or the taskbar to stop responding requiring you to open Task Manager to restart explorer.exe.