Odrive app doesn't start despite clicking

Troubleshooting
1

Hi. I have installed Odrive desktop app on my computer, Windows 7, 2 GB Ram. Despite clicking on Odrive icon, and repairing install two times, the app doesn’t start. It doesn’t show any kind of message too. What do I do?

2

Hi @bilalkmughal,
Can you try following the instructions in this post and let me know the result please?

https://forum.odrive.com/t/odrive-not-showing-in-windows-explorer/1113/11

3

Hi Tony.

The output for 1:

C:\Users\Bilal>powershell -command “&{& “$env:programfiles\odrive\odrive.exe”
”-v" 2>&1 | echo;}"

Starting launcher with verbose output…

No product argument was passed in. Attempting to find product.conf…

Using path C:\PROGRA~1\odrive\product.conf…

Using C:\Users\Bilal.odrive as the installed folder path…

Attempting to mark the installed folder path as hidden…

Writing the product.conf file at C:\Users\Bilal.odrive…

Reading the version number from the version file…

Attempting to read systemAlertRoom from config…

Setting up diagnostics for buildNo: 5926, productName: prod, systemAlertRoom: 1
358891

Creating launcher object…

Checking if another odrive process is running again to reduce the chances of a
race condition…

Launching…

Got WindowsError exception [Error 2] The system cannot find the file specified

Traceback (most recent call last):
File “”, line 177, in main
File “C:\hudson\workspace\Odrive_Win_Master_Launcher\deploy\output\artifacts
build\odrive\WinOdrive\out00-PYZ.pyz\src.odrive_app.Launcher”, line 166, in lau
nch
File “C:\hudson\workspace\Odrive_Win_Master_Launcher\deploy\output\artifacts
build\odrive\WinOdrive\out00-PYZ.pyz\src.odrive_app.Launcher”, line 120, in _la
unch_app
File “C:\hudson\workspace\Odrive_Win_Master_Launcher\deploy\output\artifacts
build\odrive\WinOdrive\out00-PYZ.pyz\subprocess”, line 711, in init
File “C:\hudson\workspace\Odrive_Win_Master_Launcher\deploy\output\artifacts
build\odrive\WinOdrive\out00-PYZ.pyz\subprocess”, line 959, in _execute_child
WindowsError: [Error 2] The system cannot find the file specified

Could not launch, which means the app is already running

(However it’s not there in task manager)

Output for 2:

C:\Users\Bilal>powershell -command "&{$bin=$(ls -Dir “$HOME.odrive\bin” | sor
t Name -desc | select -f 1).FullName; Start-Process -NoNewWindow “$($bin)\odriv
eapp.exe”;}"
Get-ChildItem : A parameter cannot be found that matches parameter name ‘Dir’.
At line:1 char:17

  • &{$bin=$(ls -Dir <<<< “$HOME.odrive\bin” | sort Name -desc | select -f 1).F
    ullName; Start-Process -NoNewWindow “$($bin)\odriveapp.exe”;}
    • CategoryInfo : InvalidArgument: (:slight_smile: [Get-ChildItem], ParameterB
      indingException
    • FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Comm
      ands.GetChildItemCommand

Start-Process : This command cannot be executed due to the error: The system ca
nnot find the file specified.
At line:1 char:94

  • &{$bin=$(ls -Dir “$HOME.odrive\bin” | sort Name -desc | select -f 1).FullNam
    e; Start-Process <<<< -NoNewWindow “$($bin)\odriveapp.exe”;}
    • CategoryInfo : InvalidOperation: (:slight_smile: [Start-Process], InvalidOp
      erationException
    • FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.C
      ommands.StartProcessCommand
4

Hi @bilalkmughal,
Strange. It looks like the Launcher is having problems finding the main odrive app.

Can you try running this command? It looks like Windows 7 doesn’t like the -Dir in the previous one:

powershell -command "&{$bin=$(ls \"$HOME\.odrive\bin\" | sort Name -desc | select -f 1).FullName; Start-Process \"$($bin)\odriveapp.exe\";}"

There should be a .odrive folder in your user home directory: C:\Users\Bilal.odrive
This fodler is hidden, so you may need to enable showing hidden files and folders in Windows Explorer to see it. Inside that directory should be a bin\5926\ directory which has the application in it.

If that directory, or some of the files inside are missing, it may be possible that something is removing them after install. Do you have any anit-virus or other applications running that actively monitor the system? If so, can you try disabling those to see if there is any difference?