On Windows 10 (build 15063.726) after update from gpg4win 2.3.3 to 3.0.1 the old DirMngr service fails to start causing windows to log an error in the event log. e.g.
Log Name: System
Source: Service Control Manager
Date: 11/25/2017 8:14:45 PM
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: elite
Description:
The DirMngr service failed to start due to the following error:
The system cannot find the file specified.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2017-11-26T02:14:45.541373200Z" />
<EventRecordID>7119</EventRecordID>
<Correlation />
<Execution ProcessID="788" ThreadID="952" />
<Channel>System</Channel>
<Computer>elite</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">DirMngr</Data>
<Data Name="param2">%%2</Data>
<Binary>4400690072004D006E00670072000000</Binary>
</EventData>
</Event>
The error log is correct, DirMngr is no longer running when checking system config -> services. If DirMngr is not supposed to be running with 3.0.1, then the entry attempting to start it wasn't removed on update. If it is supposed to run with 3.0.1 -- that's a problem.
This doesn't visibly effect the behavior of gpg4win and is more of just a log annoyance as long as DirMngr not running is the intended behavior. If so, it looks like a registry cleanup is overlooked when installing 3.0.1.
Just thought I would pass it along.