If you are running Google Drive as a windows service with AlwaysUp, beware: Google Drive is going away. The folks in Mountain View broke the news in a recent G Suite update, stating:
Google Drive will no longer be supported starting on December 11th, 2017, and it will shut down completely on March 12th, 2018.
I’m using Google Drive. What should I do?
Google isn’t leaving its users stranded. Their new Backup and Sync application is an excellent (and free) replacement for Google Drive. Just uninstall the old program, install and configure the new application and you will be good to go!
But if your goal is quickly and easily access your files in Drive from your PC, then you should also consider Drive File Stream. This new application — which will be publicly available on September 26 2017 — lists your files in Google Drive as a special folder on your PC and allows you to grab those files on demand. Drive File Stream uses less disk space than Backup and Sync, is less taxing of your network bandwidth and also boasts offline access. However, whereas Backup and Sync will happily copy files from whatever folders you designate, Drive File Stream only synchronizes the files explicitly placed in its “My Drive” folder. This may be an issue if the files you want to share span many folders across your PC. Check out this page comparing the similar products to find out which one is right for you.
One important note: Drive File Stream is not supported on Windows Server editions. This is a curious restriction for a product aimed at “G Suite Enterprise, Business and Education customers” — a group that routinely runs server products. Backup and Sync has no such limitation.
Can I run Backup and Sync as a Windows Service with AlwaysUp?
Specify it in the Application field on the General tab:
Here is a screenshot of Backup and Sync running with AlwaysUp on Windows Server 2016:
So far so good!
We will continue to test the Backup and Sync service for a couple more weeks and write up a step-by-step “setup guide” to help future customers. A tutorial for Drive File Stream will follow once that software has been officially released (near the end of 2017).
Finally, good luck migrating from Google Drive to Backup and Sync. Please don’t hesitate to get in touch if you encounter trouble running Backup and Sync as a Windows Service!
Posted onAugust 11, 2017 (Revised January 7, 2023)
AlwaysUp is designed to run Dropbox 24/7 — starting it when your PC boots and keeping your files up to date all the time despite failures or other unexpected interruptions. You don’t even need to log on!
But to gain those benefits, AlwaysUp must launch Dropbox in the background as a Windows Service. In that situation, described in our tutorial showing how to setup Dropbox as a Windows Service, Dropbox’s familiar “box” icon won’t appear on your taskbar. You won’t see the informative icon overlays beside the files and folders being synchronized either. And without those visual hints, how do you know that your important files and folders are being copied to and from the cloud?
Perform this easy 4-step test to prove that your important files are protected:
Start Dropbox in AlwaysUp
From AlwaysUp, select “Start Dropbox” from the “Application” menu:
Your service should transition to the Running state after a few seconds. Clicking on the green circle should reveal details of the running process:
Respond to that annoying email you’ve been trying to forget.
Dropbox should be ready and waiting when you return.
Create a new file in your Dropbox folder
Open your Dropbox folder in Windows Explorer. Right-click in the files area (on the right), select New > Text Document and give the file a suitable name:
We called our file “DropboxTest.txt”:
Login to Dropbox online and confirm that the new file is there
Sign in to your Dropbox account online and browse to your files. The new text file should be listed, as it was for us:
If you don’t see the new file, do a few more stretches and try again. Sometimes Dropbox can be a bit slow…
What should I do if my file didn’t show up?
If your new file wasn’t listed online, something is definitely wrong with your setup. We’re here to help! Please get in touch so that we can get you going ASAP.
A customer looking to run OneDrive as a Windows Service with AlwaysUp recently contacted our support team for help. Even though he had diligently followed our step-by-step tutorial, his files were not being synchronized as intended. OneDrive refused to refused to work as a service!
After confirming that his files were not being copied, our support team launched OneDrive “in this session” — to see the normal tray icon and check if an error was being reported. We were greeted by this puzzling error message:
So it seems that OneDrive doesn’t like to be run with admin rights. And the customer’s account was a member of the Administrators group — which is recommended for smooth operation as a Windows Service with AlwaysUp.
UAC enables an administrator to run OneDrive normally
But why does OneDrive work at all in the customer’s admin account? Why doesn’t the software complain when he starts OneDrive normally on his desktop?
The answer lies with Microsoft’s User Account Control (UAC) security feature. By default, applications started interactively are run with lower, non-admin privileges. This happens for all accounts — even for administrators. OneDrive seems to require that lower privilege context to do its work. Indeed, in this OneDrive desktop FAQ, Microsoft confirms that UAC is what enables OneDrive to be started by an administrator. If we removed UAC from the equation (by by right-clicking on OneDrive.exe and selecting “Run as administrator”) we were able to reproduce the error straightaway.
But while UAC restricts rights for the desktop user, UAC is not in play when running in the context of a windows service. Services are always run with the highest privileges. We must find a way for our customer to start OneDrive with reduced rights to avoid the error.
How to launch OneDrive with reduced rights from AlwaysUp
Our new Run with Restricted Rights command-line utility comes to the rescue. Here are the steps we performed to get the customer up and running:
where [USER-NAME] is the name of your Windows account.
Save your settings.
With this new setup, AlwaysUp will start RunWithRestrictedRights.exe, which will launch OneDrive with diminished permissions. You should not see the “full administrator rights” error anymore.
Note that we plan to add the capability to run an application with diminished rights directly from AlwaysUp. That feature will probably included in AlwaysUp version 10.3, which should released to all customers in September/October.
AlwaysUp is designed to run OneDrive all the time — starting it when your PC boots and keeping synchronization going 24×7 despite failures or other unexpected interruptions. You don’t even need to log on!
But to gain those benefits, AlwaysUp must launch OneDrive in the background as a Windows Service. In that situation, described in our tutorial showing how to setup OneDrive as a Windows Service, OneDrive’s usual “cloud” icon won’t appear on your taskbar. You won’t see the informative icon overlays beside the files and folders being synchronized either. And without those visual elements, how do you know that your important files and folders are being copied to and from the cloud?
Perform this easy 4-step test to prove that your files are protected:
Start OneDrive in AlwaysUp
From AlwaysUp, select “Start OneDrive” from the “Application” menu:
Your service should transition to Running after a few seconds. Clicking on the green circle should reveal details of the running process:
OneDrive can take a while to initialize itself — especially if it has a long list of files and folders to synchronize. This is a good opportunity for you to:
Respond to that annoying email you’ve been trying to forget.
OneDrive should be ready and waiting when you return.
Create a new file in your OneDrive folder
Open your OneDrive folder in Windows Explorer. Right-click in the files area (on the right), select New > Text Document and give the file a suitable name:
We called our file “TestSync.txt”:
Login to OneDrive online and confirm that the new file is there
Sign in to your OneDrive account and browse to your files. The new text file should be listed, as it was for us:
If you don’t see the new file, do a few more stretches and try again. Sometimes OneDrive can be a bit slow…
What should I do if my file didn’t show up?
If your new file wasn’t listed online, something is definitely wrong with your setup. We’re here to help! Please get in touch so that we can get you going ASAP.
Last month we released a new version of our popular run-anything-as-a-windows-service software, AlwaysUp. Everything was going smoothly — until we encountered a very alarming situation while testing the new software on Windows 10!
After downloading the new AlwaysUp installation executable with Microsoft Edge, the browser asserted that “AlwaysUp_Installer.exe is not commonly downloaded and may harm your computer”. WHAT??
Clicking the Actions button gave us the option to “Run Anyway”, and the installation completed without further incident, but the whole experience left our team worried and full of questions. Specifically:
Why did this suddenly start happening?
How will our customers react to Microsoft’s unfounded suspicions?
And most importantly, how do we get rid of the chilling warnings?
SmartScreen Complains because our Software is “New”
Apparently we’re not the only developers tormented by SmartScreen. Warnings are common, especially for small software companies like ours. The “Criticism” section of the Wikipedia article on SmartScreen Filter says it best:
SmartScreen Filter creates a problem for small software vendors when they distribute an updated version of installation or binary files over the internet. Whenever an updated version is released, SmartScreen responds by stating that the file is not commonly downloaded and can therefore install harmful files on your system.
Only a Few Customers are Blocked by SmartScreen Filter
To date, only one customer has asked about SmartScreen’s warning. We had expected hundreds! Fortunately there are a few reasons why many customers aren’t being tripped up by Microsoft’s overly cautious approach:
Our products are digitally signed for security and authenticity. SmartScreen takes this as a positive sign and is likely to avoid prompting all customers all the time.
Prior to Windows 8, SmartScreen Filter was a part of Internet Explorer. Thus customers using Chrome or Firefox on Windows 7 and Server 2008 will never encounter SmartScreen warnings.
After testing downloads on Windows 8, 10 and Windows Server 2012 and 2016, we only received warnings on Windows 10 with Edge.
So it seems that SmartScreen warnings are largely limited to customers using Internet Explorer or Edge. Metrics gathered from our website (via the incredibly useful StatCounter) tell us that only about 11% of all visitors are using those browsers:
Time (and Good Behavior) will Disarm SmartScreen Filter
We hoped for a simple solution: Inform Microsoft that our software is 100% safe and they would promptly update their SmartScreen database to remove all warnings. All would be right with the world. But SmartScreen doesn’t work like that.
SmartScreen is reputation based. Each time someone downloads our software package and declares that it is safe to install, that executable gains some positive reputation. Once enough people have successfully installed and the accumulated reputation crosses some magic threshold, the warnings disappear. Only an established track record of doing no harm will halt the SmartScreen dogs.
Indeed, after a couple of weeks the warnings for AlwaysUp version 10 seems to have gone away:
(888) 881-CORE
Google Drive will no longer be supported starting on December 11th, 2017, and it will shut down completely on March 12th, 2018.
![OneDrive Version 23.48: Trouble Running in Session 0 [RESOLVED]](https://www.coretechnologies.com/blog/wp-content/uploads/onedrive-error-150x150-1.webp)
