Let the Cloud Reach Deep into Your Drive: Synchronizing OneDrive Elegantly with mklink

How Office 365 Nearly Blew Up My System Drive

OneDrive’s sync limitations frustrate ordinary users. mklink, however, can feel like a secret passage for advanced users.

I had recently moved one of my larger ventures—an escape room—from the build-out stage into active operation, which finally cleared a substantial part of the project backlog.

Allow me one brief promotional detour: this is our escape room, Yating, which has now been open for a while.

If you would like to know more, head this way ↓

Yating escape-room introduction and booking

Once the project entered operation, most build-stage files had been sorted, handed over, and were unlikely to change dramatically. It seemed like the right time to back them up.

My old routine was a physical backup once a week: move the laptop files to my desktop, consolidate them, and then copy everything to an external drive.

But if something happened and I could not reach the drive, the data could still become unavailable. I kept looking for a convenient cloud location as another layer.

Why Did I Choose OneDrive?

Dropbox was my first cloud service, but I increasingly used it to share files with business partners and host public files for my personal blog. I wanted a clearer separation between public and private storage, so I stopped using it for this purpose.

My Google cloud storage was already serving as backup space for shared venture files, so most familiar options were already spoken for.

Because I was involved in several ventures, the material I wanted to protect totaled roughly 500 GB—not enormous by modern standards, but certainly substantial.

Then I remembered that my Office 365 subscription included 1 TB of OneDrive storage. Wasn’t this exactly what it was for?

OneDrive was not spacious enough to feel unlimited, but it was more than adequate for important work files.

So I decided to use OneDrive as my cloud storage for work. It required no extra subscription and was already familiar.

That Sounds Smooth—So What Went Wrong?

Once I make a decision, I tend to act immediately. Without hesitation, I copied the entire work folder from drive D into my local OneDrive folder.

Just as I was about to leave it running and go to lunch, Windows warned me that drive C was running out of space.

I investigated and found that my local OneDrive folder lived inside the Users directory on the system drive. In other words, every local file consumed space on drive C.

With that setup, files had to exist inside the OneDrive folder on drive C before the client would upload them.

Wait—my files total more than 500 GB! My system drive is nowhere near that large. Good grief.

Maybe I did not need to protect all of it?

I reviewed the work folder and found that a large share consisted of podcast and online-course video files. Perhaps I could simplify things and keep only the important documents in OneDrive.

Some escape-room build files were already in shared cloud storage, so they did not need to be duplicated in my private space. After trimming, the total fell to around 50 GB—manageable on drive C.

I would simply need to develop the habit of dragging each folder into OneDrive after finishing work in its original location.

It is inconvenient, but it should work for now, I thought.

And How Did That Turn Out?

My work keeps me moving. Sometimes I work in a café, sometimes at a tutoring center, so I spend roughly half my time on a laptop rather than my desktop.

I began opening cloud files directly on the laptop, continuing the work there, and then pulling the cloud copy back into the original desktop folder when I got home.

That sounds like trouble waiting to happen, doesn’t it?

One day I rushed out and forgot to upload the half-finished work from home.

When I noticed, I decided to continue from the older version and merge everything after returning home.

The plan seemed foolproof. Instead, I accidentally used the partially edited newer copy to overwrite most of the more complete version.

An entire day of work vanished.

Fortunately, OneDrive’s version history rescued it. I will cover that recovery process in another article.

The files came back, but this routine was clearly unsustainable. Was there a way to have changes reach the cloud without moving the original folders or filling drive C?

Why Did This Problem Happen?

Leaving aside my lazy attempt to shuttle files between laptop and desktop, the underlying problem came from the OneDrive setup itself.

On first setup, OneDrive assumes that users keep their files under the Users directory, so it creates the local OneDrive folder there on drive C.

That is reasonable for people who already store everything on drive C inside their user profile.

Many users, however, reserve the faster system drive for Windows and applications while keeping large data folders on higher-capacity drives.

For someone whose work lives on drive D or E, the default arrangement appears to require moving the entire folder into OneDrive’s local path.

To preserve their original folder structure, many people copy rather than move. The same data then exists twice: once in its original location and once under OneDrive.

At hundreds of gigabytes, that duplication can consume enormous space across two drives.

Worse, Windows needs free space on drive C. When it fills up, the computer may slow down, throw errors, or fail to update.

The Workaround Copilot Suggested

I used the approach described in my AI × Learning series: before asking for a solution, I gave Copilot a detailed explanation of the problem and its context.

If you are interested in communicating with AI more effectively, see this article from the series ↓

[AI × Learning] From Not Thinking to a Thinking Loop: Why You Must Learn to Ask Before Using AI

I had already searched online, but most answers involved reinstalling software or unlinking the account and relocating the entire OneDrive folder.

Honestly, I wanted a blunt solution: point OneDrive at selected folders without reinstalling Office or moving anything.

That seemed like the most flexible approach because I could choose any folder later. Predictably, Copilot first said it could not be done.

It repeated the familiar options—relinking the account or relying on third-party software. I did not pursue them because they did not fully solve my need to choose arbitrary folders in the future.

I reframed the question: could a specific folder be synchronized without moving it from its original location?

That was when Copilot suggested the unusual approach discussed here: a symbolic link.

Symbolic Links: An Invisible Bridge in the File System

To work around OneDrive’s path on drive C while preserving my original folder structure, I ultimately tried the built-in Windows command mklink /D.

This command creates a directory symbolic link. It looks like an ordinary folder icon, but it is really an entry point that redirects to another location.

To users and applications it behaves like a folder that can be read and written, while the file system treats it as a path pointing elsewhere.

The appealing idea is to place a virtual folder inside OneDrive while its target is actually a work folder on drive E or another disk.

In my environment, OneDrive did scan and upload content from the link target while the physical files remained in place. That is an observation, not official Microsoft support or a guarantee across versions and devices.

In that successful test, I did not need to move or duplicate the data, reinstall Office, or waste additional space on drive C.

According to Microsoft’s documentation, mklink is a Windows command for creating symbolic links to files or directories._[1]

The /D option creates a directory symbolic link rather than a link to one file. It can point to another drive. Microsoft, however, explicitly states that OneDrive does not support synchronization through symbolic links or directory junctions. What follows is my tested workflow, not an officially supported procedure.

Conceptually, a symbolic link opens an invisible door in the file system. You open that door from OneDrive, but the room beyond it lies deep inside another drive.

That invisible bridge lets us redirect the flow of data without disturbing the original arrangement.

How I Set Up the Directory Symbolic Link in OneDrive

Once the idea behind mklink was clear, the next challenge was applying it to my OneDrive workflow.

First, I created a Backup folder inside the local OneDrive directory. It would hold links to different folders and keep desktop and laptop material organized.

The remaining steps take place in Command Prompt.

Open Windows Search—usually the magnifying-glass icon—and search for CMD or Command Prompt.

Creating a symbolic link commonly requires elevated privileges, so you can right-click Command Prompt and choose Run as administrator. On some Windows versions, Developer Mode permits symbolic-link creation without elevation; version and organizational policy may still affect the behavior.

When it opens, you will see the familiar black console window.

Suppose we want to create a link inside OneDrive’s Backup folder that points to the folder named “Work (completed, stored on drive)” on drive E. We would enter:

This creates a symbolic link named “Work (completed, stored on drive)” in the OneDrive Backup path and points it to the folder of the same name on drive E.

Replace the first quoted path with the location and name of the link you want inside OneDrive. Replace the second quoted path with the existing folder you want the link to target.

Do not create the link folder in advance; mklink creates it for you.

Press Enter. When the command succeeds, Windows displays a message like the following, indicating that the symbolic link was created.

C:\Windows\system32>mklink /D "C:\Users\somnus0131\OneDrive\backup\Work (completed on drive)" "E:\Work (completed on drive)" Symbolic link created for C:\Users\somnus0131\OneDrive\backup\Work (completed on drive) <<===>> E:\Work (completed on drive)

Afterward, my OneDrive client did scan and upload files from the link target. Because this is unsupported, a successfully created link does not guarantee complete or continuing synchronization.

Most changes in the original folder were detected and uploaded in my tests. I also encountered cases where detection did not fire immediately and pausing then resuming sync was needed to trigger another scan.

The folder icon resembles a shortcut, but users can otherwise open the folder and its files normally.

When I began using mklink /D for this workflow, the biggest feeling was relief.

I no longer had to move a huge folder onto drive C or tolerate the space consumed by a duplicate copy.

On my desktop, OneDrive found and uploaded most file changes. Real-time change notifications can fail, however, so I still verify the status before assuming sync is complete.

Before working on the laptop, I confirm that OneDrive has finished syncing. After saving, I wait for the upload, and I check again on the desktop. Editing the same file on two computers can still create conflict copies or overwrite versions, so the visible file cannot simply be assumed to be current.

For someone who alternates between laptop and desktop, the workaround reduced the confusion of manual copying. I still need to verify completion and avoid editing one file on multiple devices at once.

Drive C stopped filling up, the system remained stable, and I could preserve my original folder arrangement while gaining the convenience of a cloud copy.

The method has saved me considerable manual-transfer time. I still check sync status, cloud files, and version history, and I keep an independent backup so that OneDrive synchronization is never mistaken for a complete backup strategy.

Common Problems

Symbolic links can be elegant, but many people online have found that the setup does not go smoothly. Those experiences highlight the points that deserve special care.

Common Problem 1: Confusing /J with /D

The /J option creates a directory junction, while /D creates a directory symbolic link. They are different Windows link types.

This article uses /D because my scenario points to another drive and that is the configuration I tested. It does not mean OneDrive officially supports /D. Microsoft explicitly marks synchronization through both symbolic links and junctions as unsupported.

To reproduce my cross-drive test, the option is /D. Begin with non-critical data and accept that the workflow may fail or require manual intervention.

Common Problem 2: Delayed or Stalled Synchronization

After the link is created, OneDrive may not detect target-folder changes immediately. In this unsupported configuration, real-time notifications can fail; a delay should not automatically be treated as ordinary scheduling.

When that happened, I right-clicked the OneDrive cloud icon in the taskbar, opened the gear menu, and selected Pause syncing.

After confirming the pause, I repeated the steps and selected Resume syncing. This manually triggered another scan in my environment, but it is not a Microsoft-guaranteed repair for symbolic-link synchronization. Check the cloud files individually after resuming.

Common Problem 3: Conflicting Links Across Devices

Some users create the same symbolic-link name on both desktop and laptop but point it to different local folders. OneDrive can then produce conflict copies instead of reliably identifying the latest version.

My preference is to create the link only on the desktop and have portable devices edit the cloud copy directly. Even then, wait for synchronization to complete before switching devices.

Conclusion

From an Office 365 subscription, through 500 GB nearly overwhelming drive C, to overwriting files while moving between devices, I gradually realized that cloud synchronization is not merely technical. It is also about order, structure, and working habits.

In my environment, a symbolic link provided a convenient workaround that connected cloud storage with the drive without disturbing the original folder order. It nevertheless remains an unsupported OneDrive configuration.

It opens an invisible door in the file system, letting the cloud reach deep into the drive without unsettling the order already there.

If you are also looking for synchronization that leaves the original arrangement untouched, mklink may feel like the most inspired tool in the box—provided you accept its unsupported status and risks.

If you enjoy my writing, follow my Facebook page or Instagram using the links below so you do not miss new articles. I will see you in the next one!

References

[1] Microsoft Learn — mklink

[2] Microsoft Support — Restrictions and limitations in OneDrive and SharePoint

[3] Windows Developer Blog — Symlinks in Windows 10!