File Stream Path

[fiza]

It shouldn't need to be in the same folder.

 

Did you download the .zip from post #6 or post #15. The latter is what you need since v1.0 does work under standard user accounts.

 

I downloaded version 1.1 of the launcher.

 

When I run the RunFS.exe I get the hour glass for a split second and then nothing.

 

In the Event Log I am getting Errors;

 

[Arthur]

When I run the RunFS.exe I get the hourglass for a split second and then nothing.

Thanks for the event viewer screenshot.

 

Are you running the EXE on Windows 7 and which version of the .NET Framework do you have installed?

[fiza]

Thanks for the event viewer screenshot.

 

Are you running the EXE on Windows 7 and which version of the .NET Framework do you have installed?

 

Windows 7 SP1. .NET is 4.7

Edited February 22, 2018 by fiza

[fiza]

Some new updates to File Stream announced.

 

https://gsuiteupdates.googleblog.com/2018/02/new-drive-file-stream-settings-for-your.html

[tj2419]

Hi I am trying to use the second version of the file stream exe from here but staff receive an error saying:

 

 

The application installed fine and they are windows 7 sp1 32bit machines. It works fine on my Windows 10 64bit machine. Any ideas?

 

Thanks

[Arthur]

they are windows 7 sp1 32-bit machines.

That would be it! I didn't think anyone was still using 32-bit Windows.

 

The EXE I attached to post #15 was for 64-bit PCs only. I should have mentioned that.

 

The other requirement is the Windows Management Framework v3.0 (or newer) has to be installed (for PowerShell v3.0).

 

I have attached a new .zip which contains both 32-bit and 64-bit EXEs.

Google Drive File Stream Launcher v1.1 (x86 & x64).zip

[tj2419]

That would be it! I didn't think anyone was still using 32-bit Windows.

 

The EXE I attached to post #15 was for 64-bit PCs only. I should have mentioned that.

 

The other requirement is the Windows Management Framework v3.0 (or newer) has to be installed (for PowerShell v3.0).

 

I have attached a new .zip which contains both 32-bit and 64-bit EXEs.

 

Next year we wont have anymore 32bit ones, but thanks so much for re generating it

[tj2419]

That would be it! I didn't think anyone was still using 32-bit Windows.

 

The EXE I attached to post #15 was for 64-bit PCs only. I should have mentioned that.

 

The other requirement is the Windows Management Framework v3.0 (or newer) has to be installed (for PowerShell v3.0).

 

I have attached a new .zip which contains both 32-bit and 64-bit EXEs.

 

Hi Arthur,

 

Really sorry to be pestering again. When I try run the x86 version I get the error cannot find path 'C:\Program Files (x86)\Google\Drive File Stream'

 

My File stream files are in 'C:\Program Files\Google\Drive File Stream'

 

Any way you can adapt it for this? I've tried using the site in the readme but can't get my head around it.

 

Thanks

[Dwigt]

Hi Arthur,

 

Really sorry to be pestering again. When I try run the x86 version I get the error cannot find path 'C:\Program Files (x86)\Google\Drive File Stream'

 

My File stream files are in 'C:\Program Files\Google\Drive File Stream'

 

Any way you can adapt it for this? I've tried using the site in the readme but can't get my head around it.

 

Thanks

 

I've generated an x86 version of the .exe using the path you wanted, using Arthurs source files. Let me know if it works.

 

-removed, did it wrong, will regenerate and attach again in the morning

Edited April 3, 2018 by Dwigt

[tj2419]

I've generated an x86 version of the .exe using the path you wanted, using Arthurs source files. Let me know if it works.

 

-removed, did it wrong, will regenerate and attach again in the morning

 

Any luck with the newer version?

 

Thanks

[Dwigt]

Any luck with the newer version?

 

Thanks

 

Think so. Attached

 

I used Powershell ISE to make the .exe using this command:

 

.\ps2exe.ps1 RunFS.ps1 RunFSx86.exe -x86 -iconFile RunFS.ico

 

Make sure ps2exe.ps1 is in the same folder as the RunFS.ps1 and RunFS.ico files and you can do it yourself. The -x86 flag is all you need to make it a 32bit exe, afaik.

 

All I changed in the RunFS.ps1 is this line:

 

$FS = Get-ChildItem -Path "[b][color=#ff0000]${env:ProgramFiles}[/color][/b]\Google\Drive File Stream" -Directory | Where-Object { $_.Name -match '\d+\.\d+\.\d+\.\d+' } |

 

to

 

$FS = Get-ChildItem -Path "[b][color=#ff0000]C:\Program Files[/color][/b]\Google\Drive File Stream" -Directory | Where-Object { $_.Name -match '\d+\.\d+\.\d+\.\d+' } |

 

 

Zip file containing everything:gfsx86.zip

Edited April 4, 2018 by Dwigt

[Dwigt]

Any luck with the newer version?

 

Thanks

 

Did it work for you?

[tj2419]

Did it work for you?

 

Hi Sorry for the delay, I've been away.

 

Unfortunately not. I get an appcrash notification and it fails to open.

 

Cheers anyway

[jedwards2]

This is a great idea and just what I was looking for. It works on my office PC but I am coming across the crashing issue mentioned by others on student/staff PCs (I've tried generating a new EXE on my PC). Is Windows Management Framework v3.0 required on all computers that will run the EXE, or just the one that generates the EXE?

 

I've also used the source code supplied to generate an EXE that will allow File Stream to be uninstalled (when I get it all working) in case that is required later down the line.

[Arthur]

Is Windows Management Framework v3.0 required on all computers that will run the EXE

Yes. All of the computers.

 

The majority of my school PCs are running Windows 10 with a small number of Windows 7 PCs (with WMF 3.0). IIRC, I integrated WMF v3.0 into the install.wim so that it was installed out-of-the-box. It's easy to deploy post-install however.

 

I wanted to avoid having to create different scripts for PowerShell v2.0 and another for v3.0+, so I settled on v3.0 as the minimum. I thought everyone would have PowerShell v3.0 (or newer) by now.

Edited April 18, 2018 by Arthur

[Arthur]

Unfortunately not. I get an appcrash notification and it fails to open.

I think the 32-bit EXE has to be generated from within a 32-bit OS. I will give that a try (assuming @Dwigt didn't already try this?)

Edited April 18, 2018 by Arthur

[Dwigt]

I think the 32-bit EXE has to be generated from within a 32-bit OS. I will give that a try (assuming @Dwigt didn't already try this?)

 

Sorry for the slow response I did not generate it from a 32bit machine.

[Dwigt]

So I finally got round to trying this on a machine other than my own. When I run the exe as a normal domain user, I get the following error messages:

Oddly, once I click 'OK' on both of them, the File Stream folder opens as expected.Any ideas?

Edited May 23, 2018 by Dwigt

[Arthur]

So I finally got round to trying this on a machine other than my own. When I run the exe as a normal domain user, I get the following error messages:

Do you have WMF 3.0 (or newer) installed?

[Dwigt]

Do you have WMF 3.0 (or newer) installed?

Initially, it wasn't working at all. Re-read the thread and installed KB2506143 to put WMF3.0 on the machine. After that, it ran but produced those two error messages first.

 

Since then, I downloaded the latest version of ps2exe and remade the RunFS.exe using your ps1 file:

 

#Requires -Version 3.0$FS = Get-ChildItem -Path "${env:ProgramFiles}\Google\Drive File Stream" -Directory | Where-Object { $_.Name -match '\d+\.\d+\.\d+\.\d+' } | Sort-Object -Property { [Version]$_.Name } | Select-Object -Last 1 -ExpandProperty FullNameStart-Process -FilePath ('{0}\{1}' -f $FS,'GoogleDriveFS.exe')

 

Now, when I run the .exe as a standard user the console window opens, displays the two error messages, quickly closes and then File Stream is run/the folder is opened.

 

So, really, it's not terrible. It doesn't prevent anyone using it as intended and they aren't required to deal with any confusing error prompts. If I can work out what's causing the errors though, it would scratch that all-too-familiar itch.

 

Edited May 24, 2018 by Dwigt
quickly!

[Edgehill]

I'm also having this issue with "Access to the path" error messages. Most users are still able to launch file stream but for a few I have had to delete the local profile before file stream will launch.

We have windows management framework 4.0 installed.

Is anyone else having this issue, has anyone been able to resolve this?

[Arthur]

I'm also having this issue with "Access to the path" error messages.

32-bit or 64-bit Windows?

 

Also, Windows 7, 8.x or 10?

[Edgehill]

Windows 7, we have a mix of 32bit/64bit but so far I have only seen the problem on 32bit PCs.

[cakeinmilk]

I did an easy fix to the path changing by blocking updates through GPO.. we reimage enough that major updates can be pushed out when we choose.

[Garacesh]

Le necrobump, a bit.

 

Since we use the Remove common program groups from Start Menu GPO, plus a non-modifiable desktop for staff, so far none of the fixed folks have come up with would be applicable here.

However in my testing, it doesn't look like File Stream cares what the path is. It's not hard coded. It can be C:\Program Files\Google\Drive File Stream\43.0.8.0 just as much as it could be C:\Gewuigowiehgowqghwgb\WTHAmIDoingWithMyLife.

 

So, I've whipped together a little startup script should do the trick:

[color="#008000"]# Directory paths[/color]
[color="#800000"]$GDFSPath[/color] = [color="#800000"]"C:\Program Files\Google\Drive File Stream"[/color]
[color="#800000"]$GDFSCurVer[/color] = [color="#800000"]"C:\Program Files\Google\Drive File Stream\CurrentVersion"[/color]

[color="#008000"]# Get latest version of GDFS[/color]
[color="#800000"]$LatestVer[/color] = ([color="#0000FF"]Get-ChildItem[/color] [color="#800000"]$GDFSPath[/color] [color="#000080"]-Directory[/color] | [color="#0000FF"]Where[/color] {[color="#800000"]$_[/color].Name [color="#808080"]-inotmatch[/color] [color="#800000"]"Drivers|CurrentVersion"[/color]} | [color="#0000FF"]Select-Object[/color] [color="#000080"]-Last[/color] [color="#4B0082"]1[/color]).FullName

[color="#008000"]#Copy to CurrentVersion folder[/color]
[color="#0000FF"]Copy-Item[/color] [color="#000080"]-Path[/color] [color="#800000"]"$LatestVer"[/color] [color="#000080"]-Destination[/color] [color="#800000"]"$GDFSCurVer"[/color] [color="#000080"]-Recurse -Force[/color]

This should allow GDFS to update itself and still keep the shortcut location permanent.

Going to run some tests with it, but this should work.

 

(And that'd be Copy-Item -Path ((Get-ChildItem "C:\Program Files\Google\Drive File Stream" -Directory | Where {$_.Name -inotmatch "Drivers|CurrentVersion"} | Select-Object -Last 1).FullName) -Destination "C:\Program Files\Google\Drive File Stream\CurrentVersion" -Recurse -Force if anybody wants it shortened down)

 

 

Edit: Testing has shown this to work just fine, no errors at all so far.

 

After some tweaking, I've settled on:

# Google Drive File Stream creates a new directory each time it updates.
# This results in the shortcut in the redirected start menu becoming invalid or pointing to older versions.
# This script copies the latest version to the same folder to keep the newest version at the same destination with each update.

If (Test-Path -Path "C:\Program Files\Google\Drive File Stream") {

   # Get latest version folder path.
   ForEach ($Property in (Get-ChildItem "C:\Program Files\Google\Drive File Stream" -Directory | Where {$_.Name -inotmatch "Drivers|CurrentVersion"} | Select-Object -Last 1)) {
       $LatestVer = $Property.Name
       $LatestVerFullPath = $Property.FullName
   }

   # Copy the latest version to CurrentVersion folder, creates the folder if it doesn't already exist.
   Copy-Item -Path $LatestVerFullPath -Destination "C:\Program Files\Google\Drive File Stream\CurrentVersion" -Recurse -Force

   # Delete all but the latest version.
   Get-ChildItem -Path "C:\Program Files\Google\Drive File Stream" -Directory | Where {$_.Name -inotmatch "Drivers|CurrentVersion|$LatestVer"} | Remove-Item -Recurse -Force

}

 

This copies the newest version (which keeps the %ProgramData% shortcut correct, just in case) and deletes the rest. A shortcut to C:\Program Files\Google\Drive File Stream\CurrentVersion\GoogleDriveFS.exe will then always be the latest version and will work for any user. (We have a scheduled task to shut computers down at 8pm so at most it'll be a day out of date)

Edited November 16, 2020 by Garacesh