Ludwig Maier 2 Posted November 23, 2018 Hey guys, when i try to remount my p drive than cames the error message. https://imgur.com/a/hEaGIqU Yesterday it was working but now. I restalled every thing. But still the same error. Tryed different service packs but that also did not fix. I cant find anyting on google. Can some one help me pls? Share this post Link to post Share on other sites
Tom_48_97 181 Posted November 26, 2018 Hello, can you, please, run Workdrive (without parameters) and share the latest log from (common\DayZ Tools\Bin\Logs\Workdrive.YYYY.MM.DD) Share this post Link to post Share on other sites
Salutesh 2 Posted November 26, 2018 I have the same issue since today after steam updated the tools and server files, this is my log: Quote 2018-11-26 22:06:03,679 1 [INFO] [LibCommon.Logger.Start]: Logger initialized 2018-11-26 22:06:03,713 1 [INFO] [LibCommon.Logger.Start]: ===================================================================== 2018-11-26 22:06:03,719 1 [INFO] [LibCommon.Logger.Start]: WorkDrive 2018-11-26 22:06:03,726 1 [INFO] [LibCommon.Logger.Start]: == E:\SteamLibrary\steamapps\common\DayZ Tools\Bin\WorkDrive\WorkDrive.exe == 2018-11-26 22:06:03,732 1 [INFO] [LibCommon.Logger.Start]: Build: Public 2018-11-26 22:06:03,738 1 [INFO] [LibCommon.Logger.Start]: Version: 1.2.138.6803 2018-11-26 22:06:03,742 1 [INFO] [LibCommon.Logger.Start]: ProductName: WorkDrive 2018-11-26 22:06:03,746 1 [INFO] [LibCommon.Logger.Start]: ===================================================================== 2018-11-26 22:06:03,756 1 [INFO] [LibCommon.Logger.Start]: Privileges: IsProcessElevated=False IsRunAsAdmin=False 2018-11-26 22:06:03,762 1 [INFO] [LibCommon.Logger.Start]: Loaded assemblies: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 v4.0.30319 WorkDrive, Version=1.2.139.6803, Culture=neutral, PublicKeyToken=null v4.0.30319 Void Main(System.String[]) NativeMethods, Version=1.43.60.6823, Culture=neutral, PublicKeyToken=null v4.0.30319 LibCommon, Version=1.2.233.6837, Culture=neutral, PublicKeyToken=null v4.0.30319 log4net, Version=1.2.13.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a v4.0.30319 System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 v4.0.30319 System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 v4.0.30319 System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 v4.0.30319 System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a v4.0.30319 System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a v4.0.30319 System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 v4.0.30319 2018-11-26 22:06:03,769 1 [INFO] [LibCommon.Logger.Start]: System info: System/Current dir: E:\SteamLibrary\steamapps\common\DayZ Tools\Bin\WorkDrive System/Command line: workdrive System/OS Version: Microsoft Windows NT 6.2.9200.0 System/OS 64bit: True System/Process 64bit: False System/Personal dir: C:\Users\steph\Documents System/Local App Data dir: C:\Users\steph\AppData\Local 2018-11-26 22:06:03,775 1 [INFO] [LibCommon.Logger.Start]: ===================================================================== 2018-11-26 22:06:03,782 1 [INFO] [WorkDrive.Program.Main]: Build Configuration: DayZ 2018-11-26 22:06:14,186 1 [INFO] [WorkDrive.Program.ExitApplication]: ExitCode='0' 2018-11-26 22:06:14,193 1 [INFO] [WorkDrive.Program.ExitApplication]: Terminate WorkDrive Already tryed to verify the tools and game with Steam, no changes. Share this post Link to post Share on other sites
Salutesh 2 Posted November 26, 2018 (edited) Fixed my problem by simply start the DayZ Tools from Steam. Maybe some background setup things that only steam is running for you?! Edited November 26, 2018 by Salutesh Share this post Link to post Share on other sites
Tom_48_97 181 Posted November 27, 2018 Indeed, you will need to start the primary tool once to add all needed registry entries, on each update or verification of the files. As for the Ludwig's issue, it might be different because the log shows that the process is elevated. 1 Share this post Link to post Share on other sites
Ludwig Maier 2 Posted December 3, 2018 Thank u tom thats what fixed my problem too. I just started the dayz tools from steam 1 Share this post Link to post Share on other sites
Salutesh 2 Posted December 4, 2018 (edited) On 11/27/2018 at 1:43 PM, Tom_48_97 said: Indeed, you will need to start the primary tool once to add all needed registry entries, on each update or verification of the files. As for the Ludwig's issue, it might be different because the log shows that the process is elevated. Would be a very useful information for the documentation of the DayZ tools when they are there :) Edited December 4, 2018 by Salutesh 1 Share this post Link to post Share on other sites