Remove "Shielded VM Tools" capability
- Single actionThis page belongs to a script, containing basic changes to achieve a task.
- Windows onlyThis script improves your privacy on Windows
- Impact: HighSystem Functionality Loss Risk: High
This action improves privacy with high impact when you run the recommended script. - Batch (batchfile)These changes use Windows system commands to update your settings.
- Fully reversible
You can fully restore this action (revert back to the original behavior) using this website.
The restore/revert methods provided here can help you fix issues.
Overview
Missing Good Quality Documentation
This page does not yet meet PrivacyLearn's documentation standards. However, the script/action is stable and verified by community. Here are some options for you to understand its functionality:Computer-generated docs (PREVIEW)
This documentation may be low quality but still useful.Read computer-generated explanation
This documentation is automatically extracted from the code implementation.
Remove "Shielded VM Tools" capability — This section delivers precise knowledge on how. As well, this article shows the path to learning the procedure to reverse the last customization.
Confidentiality of personal matters is maintained with strong system data privacy defenses. This optimization improves system data protection settings: discover the steps that help today. Make sure you understand each instruction before acting. Rushing could lead to unnecessary mistakes.
References
- Consumer Data: Increasing Use Poses Risks to Privacy
- Data Privacy and Data Protection: The Right of User’s and the Responsibility of Companies in the Digital World.
- CISA Cybersecurity Resources
- NIST Windows Security
- ISO/IEC 27001:2022
- EFF Surveillance Self-Defense
- NIST Cybersecurity Framework
Technical Details
This tweak orchestrates optional features to minimize online data privacy guardrail risks while protected system modules. In conjunction with fix delays in the system, this can help to achieve balanced feature performance.
Explore similar guides
Gives more context about the goal of the changesReview code
Requires technical knowledge about Batch (batchfile)Edit this page to improve
Requires technical knowledge about YAML and GitThis script should only be used by advanced users.
This script is not recommended for daily use as it breaks important functionality.
Consider creating a system restore point before doing any changes.
Apply Now
Choose one of three ways to apply:
Download script
Download and run the script directly- No app needed
- Offline usage
- Easy-to-apply
- Free
- Open-source
Help
How to apply or restore "Remove "Shielded VM Tools" capability" using script
- ≈ 2 min to complete
- Tools: Web Browser
- Difficulty: Simple
- ≈ 5 instructions
- 1
Download
Download the script file by clicking on the button above.
Use button above to restore changes. - 2
Keep the file
If warned by your browser, keep the file. - 3
Open
Open the downloaded file. - 4
Exit
Once it's done, press any key to exit the window. - 5
Restart
Restart your computer for all changes to take effect.
Apply with privacy.sexy
Guided, automated application with safety checks- Recommended for most users
- Includes safety checks
- Free
- Open-source
- Popular
- Offline/Online usage
Help
How to apply or restore "Remove "Shielded VM Tools" capability" using privacy.sexy
- ≈ 3 min to complete
- Tools: privacy.sexy
- Difficulty: Simple
- ≈ 4 instructions
- 2
Choose script
- Search for the script name: Remove "Shielded VM Tools" capability
- Check the script by clicking on the checkbox.
- 3
Run
Click on ▶️ Run button at the bottom of the page.This button only appears on desktop version (recommended). On browser, use 💾 Save button.
- Apply
- Revert
PowerShell -ExecutionPolicy Unrestricted -Command "Get-WindowsCapability -Online -Name 'Rsat.Shielded.VM.Tools*' | Remove-WindowsCapability -Online"
IlBvd2VyU2hlbGwgLUV4ZWN1dGlvblBvbGljeSBVbnJlc3RyaWN0ZWQgLUNvbW1hbmQgXCIkY2FwYWJpbGl0eSA9IEdldC1XaW5kb3dzQ2FwYWJpbGl0eSAtT25saW5lIC1OYW1lICdSc2F0LlNoaWVsZGVkLlZNLlRvb2xzKic7IEFkZC1XaW5kb3dzQ2FwYWJpbGl0eSAtTmFtZSBcIl5cIlwiJGNhcGFiaWxpdHkuTmFtZVwiXlwiXCIgLU9ubGluZVwiIg==
Help
How to apply or restore "Remove "Shielded VM Tools" capability" using commands
- ≈ 2 min to complete
- Tools: Command Prompt
- Difficulty: Medium
- ≈ 3 instructions
- 1
Open Command Prompt
Open Command Prompt as Administrator. - 2
Copy code
Copy the code: - 3
Paste & run
Paste the commands into Command Prompt and press Enter to run.Some changes require a system restart to take effect
Similar Guides
Wider Goal
Guides below includes this guide to achieve a wider goal.See other more general settings that includes this one as one of its actions.These plans combine multiple privacy settings, including this one, for stronger protection.
- Remove Remote Server Administration Tools (RSAT)
- Remove not preinstalled features on demand
- Remove on-demand capabilities and features
- Remove bloatware
Same Goal
Other guides in Remove Remote Server Administration Tools (RSAT) See settings that are in the same category as this guide.Using other actions in the same category may help you achieve your goal better.
See all 19 guides
About the Creators
These people have authored this documentation and written its scripts:
undergroundwires- Certified security professional
- 7+ years experience securing banks
- Open-source developer since 2005
- EU advisor, Public Speaker, Moderator
- Open-Source Contributors
- Hundreds across the globe
- Testers, reviewers, developers
- Companies, military agencies
- Community since 2017
Reviewed By
This guide has undergone comprehensive auditing and peer review:Expert review by undergroundwires
- Verified technical accuracy and editorial standards
- Assessed system impact and user privacy risks
- Audited and verified using automated security tests
Public review by large community
- Privacy enthusiasts and professionals peer-reviewed
- Millions of end-users tested across different environments
- Audited and verified using third-party security software
History
We continually monitor our guides, their impact and other potential privacy options. We update our guides when new information becomes available. On every update, we publicly store who made the change, what has been changed, why the change was made and when the change was made.