With the “Simple Modifications” feature in Karabiner-Elements, you can easily map keys. For example, you can set the following mappings:
left_command to left_option
left_control to left_command
left_option to left_control
This helps to make the Mac keyboard behavior more consistent with Windows habits.
3. Swap Command and Control Keys
In the Simple Modifications of Karabiner-Elements, you can easily map Left Command to Left Control and Left Control to Left Command to match the key layout of Windows.
Advanced Custom Rules (Complex Modifications)
Beyond simple modifications, Karabiner-Elements also supports “Complex Modifications”. In the Karabiner-Elements application, navigate to the “Complex Modifications” tab and click the Add your own rule button to add custom rules.
Below are some common custom rule JSON codes that you can paste into the new rule editor.
1. Use the Left Shift Key to Switch Input Methods
This rule allows you to switch input methods with a short press of the left Shift key, while a long press retains its original function.
If you’re encountering errors like “This host does not support AMD-V” or “Intel VT-x is unavailable” when using VMware Workstation, VirtualBox, or other virtualization software, you likely need to disable Windows 11’s VBS (Virtualization-Based Security).
Critical Update: Starting with Windows 11 24H2, disabling VBS has become more complex. Traditional methods are no longer sufficient - you must also disable the VBS dependency for Windows Hello.
What is VBS and Why Does It Interfere with Virtual Machines?
VBS (Virtualization-Based Security) is a Windows 11 security feature that creates an isolated security environment using the Hyper-V virtualization layer. While this sounds beneficial, there’s a problem:
VBS monopolizes CPU hardware virtualization features (AMD-V or Intel VT-x)
Third-party virtualization software like VMware needs direct access to these hardware features
When VBS is running, VMware cannot gain control of hardware virtualization, causing errors
In simple terms: VBS and VMware cannot simultaneously use the same virtualization hardware.
The 24H2 Change: Windows Hello Now Requires VBS
Starting with Windows 11 24H2, Microsoft made a significant change: Windows Hello security mechanisms now depend on VBS.
This means that even if you disable VBS using traditional methods, as long as Windows Hello-related functionality remains enabled in the registry, VBS will automatically restart.
This is why many users found that:
Turned off Memory Integrity ✅
Ran bcdedit commands ✅
Modified registry settings ✅
After reboot, VBS still shows “Running” ❌
Complete Disabling Steps (For 24H2)
Prerequisites
Windows 11 (any edition: Home/Pro/Enterprise)
Administrator privileges
Virtualization enabled in BIOS (AMD-V or Intel VT-x)
Step 1: Check Current VBS Status
Press Win + R, type msinfo32, press Enter
In the System Information window, scroll down
Find the “Virtualization-based security” row
If it shows “Running” → needs to be disabled
If it shows “Not enabled” → no action needed
Step 2: Disable Tamper Protection
Open Settings (Win + I)
Go to Privacy & security → Windows Security
Click Virus & threat protection
Click Manage settings
Toggle Tamper Protection to Off
Step 3: Disable Memory Integrity
Open Settings (Win + I)
Go to Privacy & security → Windows Security
Click Device security
Click Core isolation details
Toggle Memory integrity to Off
Step 4: Disable Hyper-V Related Features
Open Command Prompt as administrator (search for cmd, right-click and select Run as administrator), then run these commands sequentially:
Find Enabled (DWORD 32-bit value) and set its value to 0
Important Notes:
After disabling this, you can still use Windows Hello normally (including PIN login)
Windows Hello simply no longer uses VBS as its security backend
This does not affect your daily usage experience
Step 6: Restart Your Computer
Close Registry Editor and restart your computer.
Step 7: Verify Results
After reboot:
Press Win + R, type msinfo32, press Enter
Check if “Virtualization-based security” shows “Not enabled”
Open VMware Workstation and try starting a virtual machine
The “AMD-V/VT-x not supported” error should no longer appear
FAQ
Q1: Why does VBS automatically re-enable after reboot?
A: Most likely because you didn’t disable the Windows Hello VBS dependency. This is a hidden mechanism added in 24H2 that must be manually disabled in the registry:
Q2: Can I still use Windows Hello and PIN login after disabling?
A: Yes! Disabling the Windows Hello VBS dependency doesn’t affect Windows Hello functionality itself - it just prevents it from using VBS as a security layer.
Q3: Do I need to disable virtualization in BIOS?
A: No! Absolutely not! Disabling virtualization in BIOS will make VMware completely unable to run. The correct approach is:
✅ Enable virtualization in BIOS (AMD-V or Intel VT-x)
❌ Disable VBS and Hyper-V in Windows
Q4: What are the security risks of disabling VBS?
A: VBS provides an additional security protection layer. After disabling:
Some advanced security features will be disabled (like Credential Guard)
Malware protection capabilities will be slightly reduced
But for ordinary users with good security habits, the impact is minimal
If your computer is primarily used for development, virtualization testing, etc., the performance gains from disabling VBS usually outweigh the security loss.
Q5: What about games (like VALORANT) that require VBS?
A: Some games’ anti-cheat systems (like Riot Vanguard) do rely on VBS. You need to choose between:
Enable VBS → Can play these games, but VMware won’t work
Disable VBS → VMware works, but these games won’t run
There’s no perfect solution unless you use dual-boot.
Q6: I have Windows 11 Home, which doesn’t have Group Policy Editor. What should I do?
A: No problem. This tutorial’s methods are entirely based on command line and registry - no Group Policy Editor needed. Home edition works fine.
Registry Modification Summary (Quick Reference)
If you want to directly see the registry locations that need modification, here’s the complete list:
Disable Windows Hello VBS dependency (24H2 critical)
All value types are DWORD (32-bit) Value.
Understanding the 24H2 Documentation Gap
The Windows Hello VBS dependency introduced in 24H2 represents a significant architectural change. This specific registry setting (DeviceGuard\Scenarios\WindowsHello) is not prominently mentioned in the mainstream documentation, which has led to confusion among users following traditional VBS disabling methods.
Community forums and discussions (such as on Reddit and Microsoft Q&A) have been instrumental in identifying this requirement. This tutorial consolidates those findings to provide a complete solution.
Conclusion
The VBS disabling process in Windows 11 24H2 is more complex than before, but with the correct steps, it can be completely disabled.
Key Points Summary:
BIOS virtualization must remain enabled ✅
Windows VBS must be completely disabled ❌
Must disable Windows Hello VBS dependency (new in 24H2) ❌
Verify results after reboot
If you have any questions, feel free to discuss in the comments. Happy virtualizing!
Widgets are a new feature introduced by Microsoft in Windows 11. Currently, the news and interest modules that are enabled by default in widgets provide various kinds of information.
Edit and save content in markdown format, which makes the format simple, easy to use, open, and easy to migrate
Support WYSIWYG mode when editing, similar to Typora
Open source, thus keeping content safe and free
Support offline use, data can be stored locally, or stored in third-party channels such as Google Drive, Github repository
Support direct copying of pictures and text on web pages and paste them directly
Open the folder and display the file directory structure, which is convenient for placing and organizing notes according to the file directory from the sidebar
Supports the creation of internal links between markdown files, which can be easily jumped
Supports relationship graphs showing internal links in documents
Optional Requirements
Supports loading plugins to extend functionality
Open the online version editor directly from the web browser, call the file API to open the local folder for editing, therefore even chromebook can use it
Software solutions
✅Logseq : Not perfect, but currently the most recommended
Advantages:
Open source, most functions are as easy to use as Obsidian, such as beautiful appearance, local data storage, support for bidirectional links and relationship graphs
There is a web version, you can directly open the local folder
Shortcomings:
The directory structure browsing is not supported, and all the notes are mixed together and it is not easy to classify. Solution: If you find a way to write a “navigation document”, similar to the Yellow Pages, and then bookmark it, and add a link to the Yellow Pages every time you add a sub-document, it may also be a convenient way to find files by category. This is still not convenient like a directory, but it can be adapted.
Does not support the rendering the md standard checkbox.
❗Notion: It is basically free and easy to use, but there is no offline version, you cannot save data locally and synchronize data in your own way, which brings hidden dangers in data security and privacy, so you cannot use it with confidence. However, it supports the use of online real-time collaboration scenarios and can be used on projects, but is not suitable for storing personal core data.
❗Obsidian: It is completely free, easy to use, and supports all requirements except open source, but it is not open source. There is currently no better option for personal use.
❗VSCode+Office Viewer plugin (based on vditor): open source, md editing function is very powerful, and there is a toolbar. But bidirectional links and relational graphs are not supported. It can be said to be a good md editor, but not a very good note editor. And this plugin does not support running in the VSCode web.
Today I wanted to practice on LeetCode, and then I opened https://github.com/phodal/2md to save the problem to local. Because I found that there were some small problems with this tool, I forked a copy and fixed some errors that it would generate when converting the content of the LeetCode problem. In this way, copy the problem of LeetCode and paste it into my 2md, and then copy the converted markdown to save it locally. Repo: https://github.com/immortalt/2md The displayed format is correct, and the effect is much better. The online address of my 2md: https://immortal-blog.github.io/tomd/
This command means to mount all host shared folders to /mnt/hgfs, which is the default operation that VMware should have done automatically. However, the folder would disappear after rebooting.
mount automatically
1
sudo nano /etc/fstab
We can edit the fstab file to write the auto-mount configuration. Just add one line:
Currently (2022-05-16), we cannot install and run VMware Workstation 16.2.3 on Ubuntu Desktop 22.04 LTS. You can installed it and see the icon, but when you try to open it, it would ask you to install some modules and would fail.
Solution
Here is a script that are verified by me that can solve the problem.
1 2 3 4 5
git clone https://github.com/mkubecek/vmware-host-modules cd vmware-host-modules git checkout workstation-16.2.3 sudo make ; sudo make install sudo modprobe -a vmw_vmci vmmon vmnet
Then you may need to reboot the host system to make VM networks working.
Conclusion
Although Ubuntu 22.04 is a LTS version, it is not stable and compatible enough to deal with daily works currently. My advice is to use Ubuntu 20.04.