Windows 10: onedrive registry repair

I have Windows 10, first installed as upgrade from Windows 8. Several years ago, due to security concerns, I wanted to remove OneDrive from my pc. Finding no online guidance, I stupidly removed all registry keys relating to OneDrive. I am an idiot!Now I want to use OneDrive, but it will not run or sync. The OneDrive folder properties shows 'File folder' rather than 'System folder'. I would imagine the only way to get this working again would be a complete reinstall of Windows, and it will take days to reinstall all my applications.Before taking this step, I wanted to see if anyone knows of a

:)

 

Windows 10 - OneDrive

Right click on the app and one of the properties has an option to not automatically start it. Uncheck, restart the computer, and it should stop. If you want to go another step further, find the OneDrive app in the start menu, right click on it and uninstall.

If that is still insufficient, there is a batch uninstaller for OneDrive available online. I can copy the code here if you need it.

 

Is there a way to repair your registry without deleting it?

I thought that sfc /scannow would work but I don't think it repairs the registry, just the .dlls.
Is there a command that repairs the registry without having to repair XP entirely? I have found that a screwed up registry is the main cause of slow bootup times. But I don't know how to repair it without deleting the registry commands of programs already installed. All I really like to do is add those commands that may have been deleted by mistake or made corrupt by mistake.

Is there a way to do this?

 

Windows 10 - OneDrive

Anyone know how to remove "OneDrive - For Business" from the Explorer navigation panel? I've tried just about every registry modification, and windows policy for "Onedrive" but they only seem to work for the consumer product, not for onedrive for business.

The onedrive product alone is so damn annoying and continues to load itself upon startup, even when it's explicitly remove from startup. It continues to automatically load and unload itself from within the startup folder... while I'm actively watching it load itself into the startup folder.