Windows 10 x64

Ask for help and report issues with the Windows version of Transmission
codger
Posts: 9
Joined: Wed Mar 14, 2018 11:48 am

Windows 10 x64

Postby codger » Wed Mar 14, 2018 11:54 am

Hello,

I am trying to install Transmission on Win 10 x64 (it has all the updates) but whenever I try to install the daemon, either during the initial install or making changes after the install I get an error.

Service 'Transmission Daemon' (Transmission) failed to start. Verify that you have sufficient privileges to start system services.


My account is a user with admin rights with UAC turned off and I tried running the installer by running it from an elevated command prompt. Perhaps there is a simple thing I am over looking?

Any ideas?

Thanks

mike.dld
Transmission Developer
Posts: 249
Joined: Wed Dec 25, 2013 10:56 pm

Re: Windows 10 x64

Postby mike.dld » Wed Mar 14, 2018 12:01 pm

Anything in the event log that might point to an issue?

codger
Posts: 9
Joined: Wed Mar 14, 2018 11:48 am

Re: Windows 10 x64

Postby codger » Wed Mar 14, 2018 12:20 pm

Yes.

This was the x86 version errors. The x64 errors are the same except the location of Transmission and daemon in the error log point to C:\Program Files instead of C:\Program Files (x86)

The Application log shows an error.

Product Transmission (version numbers) ---- Error 1920. Service 'Transmission Daemon' (Transmission) failed to start. Verify that you have sufficient privileges to start system services.

And there is this information labeled event about service control manager in the system log

Code: Select all

- System

  - Provider

   [ Name]  Service Control Manager
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4}
   [ EventSourceName]  Service Control Manager
 
  - EventID 7045

   [ Qualifiers]  16384
 
   Version 0
 
   Level 4
 
   Task 0
 
   Opcode 0
 
   Keywords 0x8080000000000000
 
  - TimeCreated

   [ SystemTime]  2018-03-14T11:40:53.045938400Z
 
   EventRecordID 20956
 
   Correlation
 
  - Execution

   [ ProcessID]  836
   [ ThreadID]  1768
 
   Channel System
 
   Computer redacted
 
  - Security

   [ UserID]  S-1-5-18
 

- EventData

  ServiceName Transmission Daemon
  ImagePath "C:\Program Files (x86)\Transmission\transmission-daemon.exe"
  ServiceType user mode service
  StartType auto start
  AccountName NT AUTHORITY\LocalService


Then a bunch of these errors

Code: Select all

A timeout was reached 3000 milliseconds) while waiting for the Transmission Daemon service to connect

details:


System

  - Provider

   [ Name]  Service Control Manager
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4}
   [ EventSourceName]  Service Control Manager
 
  - EventID 7000

   [ Qualifiers]  49152
 
   Version 0
 
   Level 2
 
   Task 0
 
   Opcode 0
 
   Keywords 0x8080000000000000
 
  - TimeCreated

   [ SystemTime]  2018-03-14T11:41:08.144102000Z
 
   EventRecordID 20964
 
   Correlation
 
  - Execution

   [ ProcessID]  836
   [ ThreadID]  1764
 
   Channel System
 
   Computer redacted
 
   Security
 

- EventData

  param1 Transmission Daemon
  param2 %%1053
   5400720061006E0073006D0069007300730069006F006E000000
Last edited by codger on Wed Mar 14, 2018 6:24 pm, edited 1 time in total.

mike.dld
Transmission Developer
Posts: 249
Joined: Wed Dec 25, 2013 10:56 pm

Re: Windows 10 x64

Postby mike.dld » Wed Mar 14, 2018 12:25 pm

Are you able to start the daemon in foreground mode (passing it the -f flag via command line)?

codger
Posts: 9
Joined: Wed Mar 14, 2018 11:48 am

Re: Windows 10 x64

Postby codger » Wed Mar 14, 2018 12:27 pm

I'm not sure how to do that.

I don't know which command to run that i should add the -f to..

mike.dld
Transmission Developer
Posts: 249
Joined: Wed Dec 25, 2013 10:56 pm

Re: Windows 10 x64

Postby mike.dld » Wed Mar 14, 2018 12:31 pm

Run the command prompt (cmd.exe) and within it execute: "C:\Program Files (x86)\Transmission\transmission-daemon.exe" -f

codger
Posts: 9
Joined: Wed Mar 14, 2018 11:48 am

Re: Windows 10 x64

Postby codger » Wed Mar 14, 2018 12:35 pm

Oh. Yes, I looked there and in appdata /local /transmission but there isn't any executable transmission-daemon.exe

there is

-create
-qt
-edit
-remote
-show

The error info in the error log was pointing to it. So... I guess if the daemon won't start when installing, it removes the exe?

mike.dld
Transmission Developer
Posts: 249
Joined: Wed Dec 25, 2013 10:56 pm

Re: Windows 10 x64

Postby mike.dld » Wed Mar 14, 2018 12:47 pm

This is weird. Do you maybe have some antivirus software that removes the file? Also, not sure if it'll help but you could try looking inside C:\Windows\Temp for a log file from installation to see if there's anything there.

mike.dld
Transmission Developer
Posts: 249
Joined: Wed Dec 25, 2013 10:56 pm

Re: Windows 10 x64

Postby mike.dld » Wed Mar 14, 2018 12:48 pm

If you select "Daemon" during installation, it'll install the file. Otherwise it won't try starting the service. It's either one or the other.

codger
Posts: 9
Joined: Wed Mar 14, 2018 11:48 am

Re: Windows 10 x64

Postby codger » Wed Mar 14, 2018 12:57 pm

Ok i'm doing the daemon install as i type this.

It does add the -daemon.exe into the transmission directory. Then the error mentioned in my OP appears with the option to retry or cancel.

Hitting retry... 10 seconds or so passes the error returns with the same options.

I click cancel.

New window: Are you sure you want to cancel? Yes / No

No brings me back to the error mentioned in the OP again

Hitting Yes, the daemon.exe disappears from the transmission directory and the installer shows Transmission (version number) Setup Wizard ended prematurely.

Only option available is Finish.

codger
Posts: 9
Joined: Wed Mar 14, 2018 11:48 am

Re: Windows 10 x64

Postby codger » Wed Mar 14, 2018 1:06 pm

"This is weird. Do you maybe have some antivirus software that removes the file? Also, not sure if it'll help but you could try looking inside C:\Windows\Temp for a log file from installation to see if there's anything there."


I only have whatever win 10 installs for a/v and i'm not getting any notifications. Ill turn it off and try. The latest thing in the temp folder is from 2 hours ago and unrelated to Transmission


I completely disabled Windows defender and tried again. Same results :(

codger
Posts: 9
Joined: Wed Mar 14, 2018 11:48 am

Re: Windows 10 x64

Postby codger » Wed Mar 14, 2018 1:18 pm

Are you the same mike.did from here?

https://github.com/transmission/transmission/issues/103

I was reading that before I signed up here.

Tharns suggestion doesn't appear to apply to win 10 users. Windows Update KB2999226 is for Win 7

https://www.microsoft.com/en-us/downloa ... x?id=49077

mike.dld
Transmission Developer
Posts: 249
Joined: Wed Dec 25, 2013 10:56 pm

Re: Windows 10 x64

Postby mike.dld » Thu Mar 15, 2018 6:57 pm

Yes, that is me. The update is for more than just Windows 7 but yes, it doesn't apply to Windows 10. The .msi package check for the needed updates is slightly broken and may not function as desired.

Just a quick though: have you tried running other executables installed? I.e. does the Qt client or the rest of utilities work? If they don't either, I'd suggest trying to manually install the Visual Studio 2015 redistributable package from https://www.microsoft.com/en-us/downloa ... x?id=53587.

codger
Posts: 9
Joined: Wed Mar 14, 2018 11:48 am

Re: Windows 10 x64

Postby codger » Fri Mar 16, 2018 4:34 am

Thanks.

I removed and reinstalled all 2015 VS packages in an attempt to get the daemon installed via the .msi. I ended up extracting the daemon.exe from the .msi and manually adding it as a service and that worked for the most part but refused to authorize remote client access even though the json file had the correct rpc settings

The Qt client or the rest of utilities install and work providing I install Transmission without selecting the daemon.

After reading other posts and forums I realized the daemon has issues period, (even when installed with the installer). So I added a registry entry for -qt.exe to load when windows starts. Remote access works fine.

Terkun
Posts: 1
Joined: Sat May 26, 2018 10:08 am

Re: Windows 10 x64

Postby Terkun » Sat May 26, 2018 10:42 am

If the Transmission Daemon service stopped working for some strange reason, first of all you need to check the settings in this configuration file:
c:\WINDOWS\ServiceProfiles\LocalService\AppData\Local\transmission-daemon\settings.json
Sometimes, this file is just damaged, for example, filled with dots. If this happens, delete this file and reinstall Transmission. The service should start. Next, configure Transmission through this file, before stopping the service. And do not forget to back up this file from time to time.

Good luck seeding!


Return to “Windows Support”