Missing information regarding reboot

[TitaniumCoder477]

PROBLEM When "chkdsk /f" is invoked on volumes in use, the user is told, "Cannot lock current drive. Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (y/n)." The docuemntation for Repair-Volume says, "OfflineScanAndFix: Takes the volume offline to scan the volume and fix any errors found (equivalent to chkdsk /f)," but does not specify how a reboot is handled. For example, will the Repair-Volume cmdlet reboot the machine right then and there? Or will it run on next reboot, whenever that is? If the latter, it does not say this. Rather it just outputs "NoErrorsFound." That is, it neither fails with an exception (that could be caught, interpreted, and handled), nor does it prompt how the user wishes to handle the s ituation.

SOLUTION The documentation for Repair-Volume needs to at least specify how a reboot is handled when a volume is locked. That is, is the endpoint rebooted right then and there, or is the action just scheduled the next time the endpoint reboots.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b6dc697b-ee07-31ec-90f1-9ce1fefe7f34
• Version Independent ID: e691576d-fcfb-2200-775b-504da087c6f8
• Content: Repair-Volume (Storage)
• Content Source: docset/winserver2012-ps/storage/Repair-Volume.md
• Product: w10
• Technology: windows
• GitHub Login: @JasonGerend
• Microsoft Alias: jgerend

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!