asked on

OneDrive Standalone Update Task gets created for each user Windows 10 1909 Enterprise

After installing Windows 10 1909 Enterprise from scratch or upgrading from Windows 10 1803:
Windows 10 1909 creates a scheduled task "OneDrive Standalone Update Task-S-1-5-21.." for each and every user logging on (runs OneDriveStandaloneUpdate.exe for each user).

This is an Enterprise Environment and OneDrive is not used at all.
Anyone knows a way to preven this?

OneDrive itself is disabled by GPO.

McKnife

I don't wknow whether these tasks can be prevented, but as for deleting them, I'd use a powershell startup script with this line:

Get-ScheduledTask | where TaskName -like "OneDrive Standalone Update Task*" | Unregister-ScheduledTask -confirm:$false

Open in new window

ASKER CERTIFIED SOLUTION

Noah

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Michael Pfister

ASKER

@McKnife: Good idea to do this as a startup script.
Still looking for a way to prevent it …

@Noah: GPO gets applied and its no malware. MS just seems to be very creative in advertising OneDrive...

Michael Pfister

ASKER

Probably found it:

A registry key is present in the default profile under Software\Microsoft\Windows\CurrentVersion\Run -> OneDriveSetup

My first test after removing this specific entry was successful. The scheduled task wasn't created anymore for a new user...

McKnife

Say, what registry key is that, Computer\HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Run ?
No OneDriveSetup present here, but the tasks are there.

Michael Pfister

ASKER

Its not under HKU\.DEFAULT but in the default users profile that gets copied during the first log on.
Now trying this batch in my task sequence:

reg load HKLM\DEFAULT_USER "C:\Users\Default\NTUSER.DAT"
reg delete "HKLM\DEFAULT_USER\Software\Microsoft\Windows\CurrentVersion\Run" /v OneDriveSetup /f 
reg unload HKLM\DEFAULT_USER

Open in new window

Worked when I tested it manually...

McKnife

Thanks, yes, that one is present here, too.