Ndtyjky

Good morning all,

I have an interesting issue with the code put together below, but first a bit of a background.

Onedrive doesn't like working with domain roaming profiles. When OneDrive is installed for a user it will install OneDrive on the PC's "Appdatalocal" folder instead of for the whole PC. This means it will use that installed version for that particular PC until it is updated to a newer version. If a user is to hotdesk from another PC where their version of Onedrive is older or newer Onedrive will fail to work for them on that PC as it pulls in account information from the roaming profile within the registry. The registry compares the version in the roaming profile to the version installed in Appdata/Local and fails to start.

The script below put together by me and the help of others (with a shoutout to tomalak) is supposed to do the following:

• Delete two DWords within "HKCU:SOFTWAREMicrosoftOneDrive"


• Remove a Key within "HKCU:SOFTWAREMicrosoftOneDrive" which corresponds to the version number for example 18.0289.187


• Delete any new folders within "LOCALAPPDATAMicrosoftOneDrive"

It will perform the last task because when you delete the 2 DWords and Key from the Onedrive key and start OneDrive it will create another folder within "LOCALAPPDATAMicrosoftOneDrive" which is around 100MB. Ideally I would like to place this script in group policy to be run on login of every user.

$oneDriveInstallDir = "$env:USERPROFILEappdatalocalMicrosoftOneDrive"

$Versionarray = 13..20



if (Test-Path $oneDriveInstallDir) {

  Stop-Process -Name "OneDrive" -Force

  $currentVersion = (Get-ItemProperty HKCU:SOFTWAREMicrosoftOneDrive -Name "Version").Version 

  Remove-ItemProperty HKCU:SOFTWAREMicrosoftOneDrive -Name "Version" -Force

  Remove-ItemProperty HKCU:SOFTWAREMicrosoftOneDrive -Name "CurrentVersionPath" -Force

  Remove-Item "HKCU:SOFTWAREMicrosoftOneDrive$currentVersion" -Force

  Start-Process $oneDriveInstallDir/OneDrive.exe

  }  

  Get-ChildItem "$env:LOCALAPPDATAMicrosoftOneDrive" -Recurse | Where-Object {

    $item = $_

    $item -is [System.IO.DirectoryInfo] -and (

        $Versionarray | Where-Object { $item.Name.Contains($_) }

    )

} | Remove-Item -Recurse -Force

Stop-Process –Name invalidprocess -ErrorAction SilentlyContinue -ErrorVariable ProcessError;



If ($ProcessError) {



    Write-Warning -Message "Some of these folders are in use.";

    }

The Problem

When the script is run it will ask if I want to carry on and delete the items requested. I don't really want it to ask, even with the force commands it still asks. The major issue is it will then start to delete all of the items within the registry OneDrive key which it shouldn't do. I have tried going through a debug before asking but can't find the reason. Please see an example of the files it's attempting to delete below:

• HKEY_CURRENT_USERSoftwareMicrosoftOneDriveClientConfigTelemetryTimeStamp


• HKEY_CURRENT_USERSoftwareMicrosoftOneDriveMigrationCompleted


• HKEY_CURRENT_USERSoftwareMicrosoftOneDriveStandaloneUpdaterSafeMode


• HKEY_CURRENT_USERSoftwareMicrosoftOneDriveUpdateXMLRescanTime

Thank you for looking.

The prompt

Use the -Confirm:$false switch with your Remove-ItemProperty and / or Remove-Item commands to get rid of the prompt.

The deletion of the OnDrive Registry Hive

If there is no value set for $currentVersion, the follwing part of your script will delete the OnDrive Registry Hive:

Remove-Item "HKCU:SOFTWAREMicrosoftOneDrive$currentVersion" -Force