VMware Workstation Performance enhancements

Posted on Updated on

There can be a multitude of factors that could impact performance of your Workstation VMs. Running a VCF 9 stack on VMware Workstation demands every ounce of performance your Windows 11 host can provide. To ensure a smooth lab experience, certain optimizations are essential. In this post, I’ll walk through the key adjustments to maximize efficiency and responsiveness.

Note: There are a LOT of settings I did to improve performance. I take a structured approach by trying things slowly vs. applying all. The items listed below are what worked for my system and it’s recommend for that use case only. Unless otherwise stated, the VM’s and Workstation were powered down during these adjustments.

Items recently covered in my VMware Workstation Gen 9: BOM1 deployment.

  • Host BIOS/UFEI Settings
    • Check out my blog under the ‘BIOS settings’ for more information.
  • Hardware Design:
    • Fast Storage: NVMe, SSD, and U.2 all contribute to VM performance
    • Placement of VM files: We placed and isolated our ESX VMs on specific disks which helps to ensure better performance
    • PCIe Placement: Using the system block diagram I placed the devices in their optimal locations
    • Ample RAM: Include more than enough RAM to support the VCF 9 VMs
    • CPU cores: Design enough CPU cores to support the VCF 9 VMs
    • Video Card: Using a power efficient GPU can help boost VM performance
  • VM Design
    • Disk Choices: Matched the VM disk type to the physical drive type they are running on. Example – NVMe physical to a VMs NVMe disk
    • CPU Settings: Match physical CPU Socket(s) to VM CPU settings.
    • vHardware Choices: When creating a VM, Workstation should auto-populate hardware settings. Best vNIC to use is the vmxnet3. You can use the Guest OS Guide to validate which virtual hardware devices are compatible.
  • Fresh Installs
    • There’s nothing like a fresh install of the base OS to be a reliable foundation for performance improvments.
    • When Workstation is installed it adapts to the base OS. There can be performance gains due to this adaption.
  • Disable Side-Channel Mitigations (Core Isolation)
    • Disabling these can boost performance, especially on older processors, but may reduce security.

New Items to help with performance

Exclude Virtual Machine Directories From Antivirus Tools

NOTE — AV exceptions exclude certain files, folders, and processes from being scanned. By adding these you can improve Workstation performance but there are security risks in enabling AV Exceptions. Users should do what’s best for their environment. Below is how I set up my environment.

  • Script:
  • Manual Steps:
    • Open Virus and Threat Protection
    • Virus & threat protection settings > Manage Settings
    • Under ‘Exclusion’ choose ‘Add or remove exclusions’
    • Click on ‘+ Add an exclusion’
    • Choose your type (File, Folder, File Type, Process)
    • File Type: Exclude these specific VMware file types from being scanned: 
      • .vmdk: Virtual machine disk files (the largest and most I/O intensive).
      • .vmem: Virtual machine paging/memory files.
      • .vmsn: Virtual machine snapshot files.
      • .vmsd: Metadata for snapshots.
      • .vmss: Suspended state files.
      • .lck: Disk consistency lock files.
      • .nvram: Virtual BIOS/firmware settings. 
    • Folder: Exclude the following directories to prevent your antivirus from interfering with VM operations 
      • VMware Installation folder
      • VM Storage Folders: Exclude the main directory where you store your virtual machines
      • Installation Folder: Exclude the VMware Workstation installation path (default: C:\Program Files (x86)\VMware\VMware Workstation\).
      • VMware Tools: If you have the VMware Tools installation files extracted locally, exclude that folder as well. 
    • Process: Adding these executable processes to your antivirus exclusion list can prevent lag caused by the AV monitoring VMware’s internal actions: 
      • vmware.exe: The main Workstation interface.
      • vmware-vmx.exe: The core process that actually runs each virtual machine.
      • vmnat.exe: Handles virtual networking (NAT).
      • vmnetdhcp.exe: Handles DHCP for virtual networks.

Power Plan

Typically by default Windows 11 has the “Balanced” Power plan enabled. Though these settings are good for normal use cases, using your system as a dedicated VMware Workstation requires a better plan.

Below I show 2 ways to adjust a power plan. 1) Using a script to create a custom plan or 2) manually make similar adjustments.

  • 1) Script: I created a script that creates a custom power plan named “VMware Workstation Performance Plan” and makes all the needed changes for my system. You can find my blog here.
  • 2) Manual Adjustments:
    • Open the power plan. Control Panel > Hardware and Sound > Power Options > Change settings that are currently unavailable
    • You might see on every page “Change settings that are currently unavailable”, just click on it before making changes.
    • Set Power Plan:
      • Click on ‘Hide Additional Plans’.
      • Choose either “Ultimate Performance” or “High Performance” plan and then click on “Change plan settings”
      • Hard Disk > 0 Minutes
      • Wireless Adapter Settings > Max Performance
      • USB > Hub Selective Suspend Time out > 0
      • PCI Express > Link State Power Management > off
      • Processor power management > Both to 100%
      • Display > Turn off Display > Never

Lastly, make sure the correct power plan is active. I used the commands ‘powercfg -list’ to show the active plan and then ‘powercfg -setactive GUID’, replacing GUID with the plan I wanted.

Power Throttling (Not very common)

Power throttling in Windows 11 is an intelligent, user-aware feature that automatically limits CPU resources for background tasks to conserve energy and extend battery life. By identifying non-essential, background-running applications, it reduces power consumption without slowing down active, foreground apps.

To determine if it is active go in to System > Power and look for Power Mode

If you are using a high performance power plan usually this feature is disabled.

If you are running a power plan where this is enabled, and you don’t want to disable it, then you can maximize your performance by disabling power throttling for the Workstation executable.

powercfg /powerthrottling disable /path “C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe”

Sleep States

Depending on your hardware you may or may not have different Sleep states enabled. Ultimately, for my deployment I don’t want any enabled.

To check if any are from a command prompt type in ‘powercfg /a’ and adjust as needed.

Workstation Memory Page files

In my design I don’t plan to overcommit physical RAM (640GB ram) for my nested VM’s. To maximize the performance and ensure VMware Workstation uses the physical memory exclusively, I follow these steps: Configure global memory preferences, Disable Memory Trimming for each VM, Force RAM-Only Operation, and adjust the Windows Page Files.

Configure Global Memory Preferences

  • This setting tells VMware how to prioritize physical RAM for all virtual machines running on the host. 
    • Open Workstation > Edit > Preferences > Memory
    • In the Additional memory section, select the radio button for “Fit all virtual machine memory into reserved host RAM”.

Disable Memory Trimming for each VM:

  • Windows and VMware use “trimming” to reclaim unused VM memory for the host. Since RAM will not be overallocated, I disable this to prevent VMs from ever swapping to disk.
    • Right-click your VM and select Settings
    • Go to the Options tab and select the Advanced category.
    • Un-Check the box to disable memory page trimming.
    • Click OK and restart the VM

Force RAM-Only Operation (config.ini):

  • This is an advanced step that prevents VMware from creating .vmem swap files, forcing it to use physical RAM or the Windows Page File instead.
  • Close VMware Workstation completely.
  • Navigate to C:\ProgramData\VMware\VMware Workstation\ in File Explorer (Note: ProgramData is a hidden folder).
  • Open the file named config.ini with Notepad (you may need to run Notepad as Administrator).
  • Add the following lines to the end of the file:
    • mainMem.useNamedFile = “FALSE”
    • prefvmx.minVmMemPct = “100”
  • Save the file and restart your computer

Windows Page Files

  • With 640GB of RAM Windows 11 makes a huge memory page file. Though I don’t need one this large I still need one for crash dumps, core functionality, and memory management. According to Microsoft, for a high-memory workstation or server, a fixed page file of 16GB to 32GB is the “sweet spot.” I’m going a bit larger.
  • Go to System > About > Advanced system Settings
  • System Properties window appears, under Performance choose ‘Settings’
  • Performance Options appears > Advanced > under Virtual memory choose ‘change’
  • Uncheck ‘Automatically manage paging…’
  • Choose Custom size, MIN 64000 and MAX 84000
  • Click ‘Set’ > OK
  • Restart the computer

Windows Visual Effects Performance

The visual effects in Windows 11 can be very helpful but they can also minimally slow down your performance. I prefer to create a custom profile and only enable ‘Smooth edges of screen fonts’

  • Go to System > About > Advanced system Settings
  • System Properties window appears,
  • On the Advanced Tab, under Performance choose ‘Settings’
  • On the Visual Effect tab choose ‘Custom’ and I chose ‘Smooth edges of screen fonts’

Disable BitLocker

Windows 11 (especially version 24H2 and later) may automatically re-enable encryption during a fresh install or major update. By default to install Windows 11 it requires TPM 1.2 or higher chip (TPM 2.0 recommended/standard for Win11), and UEFI firmware with Secure Boot enabled. BitLocker uses these features to “do its work”. To disable I do the following.

  • Registry Edit (Post-Installation – may already be set):
    • Press Win + R, type regedit, and press Enter
    • Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BitLocker
    • Right-click in the right pane, select New > DWORD (32-bit) Value
    • Name it PreventDeviceEncryption and set its value to 1
    • Disable the Service:
      • Press Win + R, type services.msc, and press Enter.
      • Find BitLocker Drive Encryption Service.
      • Right-click it, select Properties, set the “Startup type” to Disabled, and click Apply.

Clean out unused Devices:

Windows leaves behind all types of unused devices that are hidden from your view in device manager. Though these are usually pretty harmless its a best practice to clean them up from time to time.

The quickest way to do this is using a tool called Device Cleanup Tool. Check out my video for more how to with this tool.

Here is Device Cleanup Tool running on my newly (<2 months) installed system. As you can see unused devices can build up even after a short time frame.

Debloat, Clean up, and so much more

There are several standard Windows based features, software, and cleanup tools that can impact the performance of my deployment. I prefer to run tools that help optimize Windows due to their ability to complete tasks quickly. The tool I use to debloat and clean up my system is Winutil. It’s been a proven util for not only optimizing systems, installing software, updates, but helping to maintain them too. For more information about Winutil check out their most recent update.

For ‘Tweaking’ new installs I do the following:

  • Launch the WinUtil program
  • Click on Tweaks
  • Choose Standard
  • Unselect ‘Run Disk Cleanup’
  • Click on Run Teaks

Additionally, you may have noticed Winutil can create an Ultimate Preforamnce power plan. That may come in handy.

Remove Windows Programs:

Here is a list of all the Windows Programs I remove, they are simply not needed for a Workstation Deployment. Some of these can be removed using the WinUtil most I remove with Revo Uninstaller Free Edition.

  • Cortana
  • Co-polit
  • Camera
  • Game Bar
  • Teams
  • News
  • Mail and Calendar
  • Maps
  • Microsoft OneDrive
  • Microsoft to do
  • Movies and TV
  • People
  • Phone Link
  • Solitare
  • Sticky Notes
  • Tips
  • Weather
  • Xbox / xbox live

References and Other Performance Articles:

Installing VMware Workstation Pro 26H1

Posted on Updated on

Here are the steps I took to install VMware Workstation Pro 26H1.

Meet the requirements

The number one issue why Workstation doesn’t install is failure to read the requirements. Ensure your hardware and your BIOS settings meet the requirements prior to installation.

Download Workstation

I’ll need to download VMware Workstation Pro 26H1. The good news is, it’s free and users can download it at the Broadcom support portal. Once you log in, you can find it under the downloads section under FREE Downloads. Need more guidance on the portal, see this KB.

Note: Make sure you click on the ‘Terms and Conditions’ plus the check box (1) before you click on the download icon (2).

Windows Settings

Disable Windows Virtualization Settings

If you are deploying Workstation on to Windows the disablement of Hyper-V and Device Guard conflicts are important. Basically, Workstation needs these to be disabled to achieve optimal performance plus support nesting. If they are not disabled the following error will appear during the installation of Workstation.

Note: Before starting, I create a current Windows restore point prior to making the following changes.

To resolve this, I used the Microsoft Device Guard and Credential Guard Hardware Readiness Tool.

  1. Download the Device Guard and Credential Guard hardware readiness tool from Microsoft.
  2. Extract the downloaded ZIP file.
  3. Use the tool to disable Device Guard and Credential Guard:
    • Open PowerShell window as an administrator.
    • Navigate to the folder where you extracted the tool.
    • First run this command to get Execution Policy:
      • Set-ExecutionPolicy Unrestricted -Scope Process
    • Now run the script with the -Disable parameter to disable Device and Credential Guard
      • DG_Readiness_Tool_v3.6.ps1 -Disable
  4. Reboot your computer.
  5. During the boot process, Windows will ask you to confirm the changes. Follow the on-screen instructions to proceed (Just press F3).
  6. When complete your computer will reboot.

Workstation Installation

Launch the Workstation program and when prompted click Next.

Check Accept and Click Next.

Ensure VMs are running on VMware Hypervisor.

Ensure directory is correct and click next.

Click next to accept auto updates and joining the CEIP program.

Click next to create shortcuts.

Click Install to install Workstation.

Allow the installer to complete and click Finish to finalize.

Open Workstation > Help > about to to validate install.

VMware Workstation Pro 26H1 is here and, its got a 64-Bit upgrade!!

Posted on Updated on

The latest update to VMware Workstation Pro, version 26H1, has officially arrived! Whether you are a developer, a sysadmin, or a tech enthusiast, this release brings a host of updates designed to streamline your virtualization workflow and expand compatibility with the latest operating systems.

Personally, I’m excited to try out is new added support for 64-Bit applications/binaries.

What’s New

  • VMware Workstation Pro 26H1 contains security and bug fixes.
  • Added support for 64-Bit VMware Workstation Pro for Windows: VMware Workstation Pro for Windows is now available as a 64-bit application and all binaries, libraries, installer components, and related services are delivered and executed as 64-bit processes.
  • Recording and reporting time stamps: You can easily identify virtual machines virtual machines by creation and last powered-on time stamp.
  • Added support for remote connections to ARM-based ESX hosts, enabling basic virtual machine operations.
  • Displaying virtual machine notes in folder tabs.
  • Updated the saved credential format: You can easily identify encrypted virtual machines and remote server in the credential manager of the host platform.
  • Added support for guest operating systems.
    • Guest operating systems
      • Ubuntu 26.04 LTS
      • Fedora 43
      • Fedora 44
      • SUSE Linux Enterprise 16
      • openSUSE 16.0
      • FreeBSD 15.0
  • Added support for Host operating systems
    • Ubuntu 26.04 LTS
    • Fedora 43
    • Fedora 44
    • SUSE Linux Enterprise 16 GA
    • openSUSE 16.0

Reminder: Workstation Pro is Now Free!

In case you missed the recent shift, VMware Workstation Pro is now free for personal, commercial, and educational use. You no longer need a license key to unlock the full power of the industry-standard desktop hypervisor. Just download, install, and start building.

Final Thoughts

The 26H1 release is a solid step forward, focusing on the “latest and greatest” in the OS world while giving power users better tools for customization. If you haven’t updated yet, now is the time to head over to the Broadcom Support Portal and grab the latest build.

Ready to upgrade? Check out the full technical details and resolved issues list in the official release notes.

VMware Cloud Foundation 9.1 (VCF 9.1) key events, webinars, and Resources

Posted on Updated on

Below is a summary of some of the great announcements around the VCF 9.1 release.

Discover What’s New in VCF 9.1

Watch this recording to see the new features in action through demo-walkthroughs and discover how the newly announced partnerships will expand VCF 9.1 capabilities.

Modules:

Learn More

Strategic Roadmap & Training

The following schedule outlines key opportunities to engage with VCF experts and the broader Broadcom ecosystem in 2026. The marquee event, VMware Explore 2026, returns to Las Vegas in late August.

DateEvent / Webinar NameLocation / Type
May 5, 2026Broadcom’s VMware in 2026: VCF 9, Containers, and AIWebinar (On-Demand)
May 13-15, 2026VCF Experience Day (Hosted by TD SYNNEX)Dallas/Plano, TX
Aug 31 – Sep 3, 2026VMware Explore 2026 Las VegasLas Vegas, NV
Sep 29-30, 2026VMware Explore on Tour: MumbaiMumbai, India
Oct 1-2, 2026VMware Explore on Tour: SingaporeSingapore
Oct 13-14, 2026VMware Explore on Tour: FrankfurtFrankfurt, Germany

Virtually Speaking Podcast Series and others

Hosted by Pete Flecha and John Nicholson, the Virtually Speaking Podcast provides weekly technical deep dives into the VCF 9.1 ecosystem. The new “VCF 9 Core” series features product engineers explaining the architectural changes.

Episode 1: Introducing VCF 9.1: Built for Efficiency and ResilienceEpisode 6: VCF 9.1: From AI Hype to Production Reality
Episode 2: From Infrastructure to Innovation: VCF 9.1 Core ExplainedEpisode 7: VCF 9.1: Scaling Secure Edge Deployments
Episode 3: VCF 9.1: Automation, Kubernetes APIs, and Faster DeploymentsEpisode 8: VCF 9.1 Cyber Resilience: From Attack to Recovery with Confidence
Episode 4: Inside VCF 9.1: Platform, Lifecycle, and What’s Different NowEpisode 9: Designing VCF 9.1: Architecture, Sizing, and Scale in Practice
Episode 5: From Rising Costs to Smarter Storage: The VCF 9.1 Reality

Resources & Documentation

Critical Reference Materials

  • Product News Release: Broadcom Announces VMware Cloud Foundation 9.1
  • Broadcom TechDocs: TechDocs have been completed updated making it easier to find content.
  • Release Notes: The full VCF 9.1 Release Notes detail the specific upgrade paths from VCF 5.x.
  • VCF Import Guide: Technical documentation on how to prepare brownfield vSphere clusters for ingestion.
  • Private AI Reference Architecture: A comprehensive guide on sizing GPU clusters and configuring vSAN ESA for high-throughput AI training.

Tech Blogs

Coming Soon

HOL

  • Test-Drive VCF 9.1 and more for free
  • What’s New in VCF 9.1
  • Memory Tiering in VCF 9.1
  • Native Kubernetes Workloads on VCF 9.1

Solution Architecture Guides

  • Self-Service Multi-tenant Private Cloud Consumption
  • Private AI Service Deployment and Consumption with VCF 9.1
  • VCF Edge Design for Retail, Manufacturing
  • Flexible Storage Deployment Models

Next Steps

For organizations planning their upgrade path, the immediate next step is to audit current hardware compatibility against the VCF 9.1 HCL (Hardware Compatibility List), particularly if planning to leverage the new NVMe memory tiering capabilities.

REF: See the follow URL for more updates. https://go-vmware.broadcom.com/whats-new-in-vcf

Managing the SDDC Installer admin@local Account – Password Resets and lockouts

Posted on

We’ve all been there. We deploy an appliance and then we can’t find the password. We try to log in a few times and the accout gets locked out. For administrators managing VMware Cloud Foundation (VCF), the admin@local account is a critical account. Introduced to provide access to the SDDC Manager APIs and the VCF Installer even when the management vCenter Server or Identity Provider (SSO) is unavailable, it ensures you aren’t locked out of your environment during critical failures.

Phase 1: Resetting the Forgotten Password

If you don’t know the current password, you must manually inject a new one via the SDDC Manager console. This process involves creating a secure credential file and hashing your new password using OpenSSL.

According to KB 403099, follow these steps on the SDDC Manager VM:

  1. Access the Console: Log in to the SDDC Manager via SSH as the vcf user, then switch to root: su - or simply logon as root.
  2. Initialize the Security Directory: Ensure the local security directory exists with the correct permissions:
    mkdir -p /etc/security/local chown root:vcf_services /etc/security/local && chmod 650 /etc/security/local
  3. Create the Password File: Create an empty file to house the secret:
    echo -n "" > /etc/security/local/.localuserpasswd chown root:vcf_services /etc/security/local/.localuserpasswd && chmod 660 /etc/security/local/.localuserpasswd
  4. Generate the New Password: Replace You Password here in the command below with a password that meets the VCF requirements (12-127 characters, including uppercase, lowercase, numbers, and special characters):
    echo -n 'Your Password Here' | openssl dgst -sha512 -binary | openssl enc -base64 | tr -d '\n' > /etc/security/local/.localuserpasswd
  5. Restart Services: Apply the change by restarting the SDDC Manager services:
    /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh

Phase 2: Unlocking the Account

Even with a fresh password, if the account was previously locked due to too many failed attempts, the system may still reject your login. You must now clear the lockout state.

Based on KB 403316, you can clear the lockout by restarting the common services component:

  1. Stay in the Console: From your existing root session on the appliance (or via the VCF Installer appliance if that is where the lockout occurred).
  2. Clear the Lockout: Run the following command to restart the service responsible for authentication:
    systemctl restart commonsvcs
  3. Final Verification: Wait a moment for the service to initialize, then attempt to log in to the web interface using the new password you created in Phase 1.

Summary

When you are locked out of your VCF environment and have forgotten your credentials, the path to recovery is a two-step process. By first following KB 403099 to manually reset the password via the command line, and then following KB 403316 to restart the commonsvcs and clear the lockout, you can regain control of your SDDC Manager and VCF Installer.

GL.iNet Comet (GL-RM1) a handy single KVM Over IP

Posted on Updated on

Recently I was working on my Ubuntu 25 workstation and I needed a way to reliably remote into the system. This Workstation uses a Supermicro motherboard. It has built in IPMI (remove KVM) but the it only supports remote KVM to the on board video card. xrdp was other option but it is no longer supported under Ubuntu 25. Using Microsoft RDP to Ubuntu desktop or remote sharing constantly disconnected, had issues, or would show black screens. The VNC options I looked at were either buggy or had a subscription fee. Other options like Team Viewer, and No Machine either cost too much or simply were too complex.

Enter the GL.iNet Comet (GL-RM1) It is a specialized hardware-based KVM-over-IP (Keyboard, Video, Mouse) device designed to give you complete remote control over a computer event at the BIOS level. Unlike software solutions, the Comet allows you to access a machine even if the operating system has crashed or hasn’t booted yet.

Key Features

FeatureSpecification
Max Resolution4K @ 30fps (also supports 2K @ 60fps)
ProcessorQuad-core ARM Cortex-A7
Memory / Storage1GB DDR3L RAM / 8GB eMMC Storage
Connectivity1x Gigabit Ethernet port (No built-in Wi-Fi)
Remote AccessTailscale integration, GoodCloud, and local web UI
PortsHDMI In, USB-C (Keyboard/Mouse), USB 2.0 (Expansion)
Dimensions80 x 60 x 17.5mm; 85g

What I like and don’t like about it:

Pros

  • Feature Rich: For a “budget” KVM over IP the amount of well laid out features and settings is a huge plus.
  • BIOS-Level Access: It’s nice to have full control over the workstation. I can remotely troubleshoot a PC before the OS loads, allowing for remote OS installations and BIOS setting changes.
  • Ease of Setup: Once I found its IP on my network it was very simple to set up. The web interface is designed very well and works great.
  • Toolbox feature: (Fig-1): The Clipboard allows for pasted text to be pasted into a remote device. It also has keyboard shortcuts, WOL, and Terminal access
  • Virtual Media and Accessories (Fig-1): It has ~5.5GB of built in storage to mount to the remote host or via the Accessories I can mount a USB memory stick.
  • Compact Design: Roughly the size of a computer mouse, making it highly portable for field technicians.
  • Mouse Jiggle: Has a feature to enable mouse jiggle on the remote system to keep the remote desktop from locking.
  • Remote Cloud Access: I have not tried this feature but you can set it up to be accessed over the internet.

Cons

  • No Built-in Wi-Fi: The standard GL-RM1 requires a wired Ethernet connection for internet access.
  • USB 2.0 Only: The expansion port is limited to USB 2.0 speeds, which may be slow for large virtual media transfers.
  • Power Requirements: It cannot be powered by some PD (Power Delivery) adapters and requires a standard 5V/2A source.
  • Limited High-Speed Video: While it supports 4K, it is capped at 30fps, which is sufficient for productivity but not ideal for gaming or smooth video playback.

What could be better:

  • Video Display: The initial video display looks a bit pixelated, but with a few video quality changes it works well. It’s totally usable but even in lossless mode it could be a bit more clear.
  • The ESC Key: To exit the remote screen you have to push the ESC key or hold the ESC key to exit full screen. Sometimes this ESC key is registered by the remote system and can cause unexpected behaviors. Example – Press ESC and your current window closes out. A work around I found with Windows was to press ALT + TAB and it releases the mouse back to the local OS.
  • Mouse Movement: Initially there are two mouse icons (local and remote) and a bit of a delay between them. A few changes in the mouse settings and the experience is much better. Would rather see these be the default settings. Mouse speed is a bit slow, a simple adjustment to the OS mouse speed is helpful.
  • High CPU: when running HTML interface in Chrome I notice my laptop fan start up and Chrome uses a lot of RAM. I simply switched to the Brave browser and it works great. Could be something about my setup and Chrome.

How It Compares

The GL.iNet Comet occupies a unique “budget-friendly” tier in the IP-KVM market.

  • Vs. PiKVM: While the PiKVM is highly expandable and open-source, it often requires buying a Raspberry Pi separately and assembling it, which can end up being more expensive and bulkier. The Comet is a “plug-and-play” alternative that is significantly cheaper as a complete package.
  • Vs. JetKVM: The JetKVM includes a local display for easier on-site monitoring, whereas the Comet is more minimalist. However, users have noted that the Comet’s availability and stability for remote connections (via GoodCloud/Tailscale) make it a very competitive choice.
  • Vs. Comet PoE (GL-RM1PE): The PoE variant is slightly larger but allows you to power the device and provide data through a single cable, which is a major advantage for clean server rack setups.

Summing it up

The Comet (GL-RM1) is working out well for my home lab as I needed reliable remote access into my workstation. To me, its primary advantage is providing a reliable, cost effective, feature rich, and quick way to do remote access with out having to install and maintain buggy software based remote access.

Deploying the ASUSTOR DRIVESTOR 4 Pro Gen 2 | AS3304T v2

Posted on Updated on

For years, my trusty DRIVESTOR 2 Pro was the heartbeat of our home. From kids navigating online school to adults working from home, it served as our essential, daily hub for family backups. Unfortunately, a sudden power event had other plans for it.

While I was lucky enough to have my data backed up elsewhere. In this post, I’ll walk you through how these two models compare, share some photos of the new hardware, and show you exactly how I got my new setup up and running.

Device Compare

ASUSTOR AS3302T (Gen 1)ASUSTOR AS3304T v2 (Gen 2)
Drive Bays 2 x 3.5″/2.5″ SATADrive Bays 4 x 3.5″/2.5″ SATA
Processor Realtek RTD1296 (1.4GHz Quad-Core)Processor Realtek RTD1619B (1.7GHz Quad-Core)
Memory (RAM) 2GB DDR4 (Non-expandable)Memory (RAM) 2GB DDR4 (Non-expandable)
Networking 1 x 2.5-Gigabit EthernetNetworking 1 x 2.5-Gigabit Ethernet
USB Ports 3 x USB 3.2 Gen 1USB Ports 3 x USB 3.2 Gen 1
Btrfs Support No (EXT4 only)Btrfs Support Yes (Snapshots supported)
RAID OptionsSingle, JBOD, RAID 0, 1RAID OptionsSingle, JBOD, RAID 0, 1, 5, 6, 10
FAN/Size 1 x 70mm
Standby/Idle Noise 19db
Active Operation Noise 32db
FAN/Size 1 x 120mm
Standby/Idle Noise 19.7db
Active Operation Noise 32db
Power Consumption 12.3W (Operation)Power Consumption 25.1W (Operation)
Dimensions 170(H) x 114(W) x 230(D) mmDimensions 170(H) x 174(W) x 230(D) mm

Key Improvements in the AS3304T v2

  • Processor & GPU: The v2 uses the newer RTD1619B chip. It is roughly 20% faster in clock speed and features an upgraded iGPU, which provides significantly better 4K transcoding for media players like Plex.
  • Modern File System (Btrfs): A major software upgrade for the v2 models is the addition of Btrfs support. This enables Snapshots, which protect your data against accidental deletion or ransomware by allowing you to “roll back” to a previous state.
  • Storage Flexibility: Beyond having twice the bays, the AS3304T v2 supports RAID 5 and 6. These configurations offer a better balance of high capacity and data redundancy compared to the RAID 1 limit of the 2-bay AS3302T

Product Photo

Initial Setup

I plugged in the power and the network cable into the device and allowed it to get a DCHP address. To find the address assigned I downloaded and scanned my network with the ASUSTOR Control Center (acc.asustor.com). One I knew the IP address I went to it on port 8001.

When I first entered the web interface I was welcomed by the main screen. One important note is the orange initialization statement. It notes your drive will be erased and a warning to backup your data.

One thing I like about the initial setup is the ability to update the ADM (ASUSTOR Data Master) version. I allowed it to update as I was doing my install.

After I made all my selections, then ADM completes it pre-tasks.

Next, the T&Cs are presented.

I get to choose my system appearance.

I entered my information.

The system does its final initialization.

I enter in my ASUSTOR ID and then on next page put in your Contact information, region, and language

All done!

Back in the web interface, I’m prompted to adjust my http and https ports. I change them from the defaults of 8000 and 8001.

The ADM guide appears and it is a good way to learn where things are. I’m not going through all 6 steps but just know its a very hand tool.

Here is what the first one looks like.

It actually takes you step by step.

Once I exit the ADM guide, I first set up my network address. Settings > Network > change to manual IP > enter my IP and save it. The web interface reboots into the new IP. Additionally, I disabled IPv6.

Next I go into the Storage Manager and validate my disks. It also gives me a status of the RAID 5 initialization.

Then in Access Control I’ll setup a few user accounts.

While in Access Control, I setup shared folder. The add shared folder window appears, I name my share, select access ‘by user’, choose the user and their access rights, chose to encrypt of not, and click on finish to complete the process.

From my experience ADM is a very intuitive and easy to learn. Speaking of learning, ASUSTOR has a FREE NAS Tutorial that explains how to use it! I’ve used it quite a bit is worth a look.

While losing my original DRIVESTOR 2 Pro was a headache, the jump to the DRIVESTOR 4 Pro Gen 2 has been a massive silver lining. With the extra drive redundancy of RAID 5, I feel much more secure about our family’s digital files. It’s faster, quieter, and handles our school and work-from-home needs without breaking a sweat. If you’re looking for a NAS that balances power with a genuinely easy learning curve, ASUSTOR remains my top recommendation.

Adjusting Windows 11 Power plan for max performance with Workstation 25H2u1

Posted on Updated on

Windows 11 power plans are a great way for idle PCs to save power when not in use. However, when using a PC in a Workstation deployment having a power plan enabled can really have some adverse outcomes. In this blog post I document how I used PowerShell to create a custom power plan and adjust the power settings for my Workstation deployment.

NOTE: You cannot just cut, paste, and run the script below. There are parts of it that have to be configured for the indented system.

What the script does

This script will make a copy of the High Performance power plan, give it a new name, and adjust/disable the following settings.

  • Sleep/Standby
  • Hibernation
  • Screen Time Outs
  • CPU to MAX
  • USB Suspend
  • Hard disk turn off
  • Disable power throttling for the workstation executable

Prerequisite

  • PowerShell 7.x
  • Visual Studio Code
  • Knowing your device GUIDs

How to get the device GUIDs

Section 4 of ‘The Script’ requires unique GUIDs. This PowerShell command create a text file with the GUIDs I’ll need. Read the comments in section 4 for more information.

powercfg /list | Out-File -FilePath "$home\Desktop\PowerGUIDs.txt"

The Script

# Run as Administrator is required for these commands
if (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
  Write-Warning "Please run this script as an Administrator."
  exit
}
# 1. Create the new Workstation Performance plan
# Duplicate High Performance
$output = powercfg -duplicatescheme 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
# Use Regex to grab ONLY the GUID from the text
if ($output -match "([a-z0-9]{8}-([a-z0-9]{4}-){3}[a-z0-9]{12})") {
  $cleanGuid = $matches[1]   
  # Rename and Activate
  powercfg -changename $cleanGuid "VMware Workstation Performance Plan"
  powercfg -setactive $cleanGuid
  Write-Host "Success: Plan '$cleanGuid' created and renamed." -ForegroundColor Green
}
powercfg -setactive $cleanGuid

# Adjust the New Workstation Performance Plan
# 2. Disable Sleep, Hibernate, and Screen Timeouts (for both AC and DC)
# Setting value to 0 means "Never"
powercfg -change -monitor-timeout-ac 0
powercfg -change -monitor-timeout-dc 0
powercfg -change -standby-timeout-ac 0
powercfg -change -standby-timeout-dc 0
powercfg -hibernate off
Write-Host "Disabled -- Sleep, Hibernate, and Screen Timeouts (for both AC and DC)" -ForegroundColor Green
powercfg -setactive $cleanGuid

# 3. CPU To MAX

# Set Min/Max Processor State to 100% (Plugged In)
powercfg -setacvalueindex $cleanGuid SUB_PROCESSOR PROCTHROTTLEMIN 100
powercfg -setacvalueindex $cleanGuid SUB_PROCESSOR PROCTHROTTLEMAX 100

# Optional Set thresholds for Battery power as well
powercfg -setdcvalueindex $cleanGuid SUB_PROCESSOR PROCTHROTTLEMIN 100
powercfg -setdcvalueindex $cleanGuid SUB_PROCESSOR PROCTHROTTLEMAX 100
Write-Host "Processor thresholds for are now locked at 100%." -ForegroundColor Green
powercfg -setactive $cleanGuid

# 4. Disable USB Selective Suspend
# NOTE -- GUIDs in this section are unique and will need to be changed to match the intended system
# Run this command to create a list of devices and GUIDs  powercfg /QH > "$env:USERPROFILE\Desktop\PowerSettings.txt"
# Search the text file for USB Setting to find the First and Second GUIDs needed below
# In the text file the First GUID is a group name 'Subgroup GUID: 2a737441-1930-4402-8d77-b2bebba308a3 (USB settings)'
# Directly below the First GUID locate the Second GUID for the 'Power Setting GUID: 0853a681-27c8-4100-a2fd-82013e970683 (Hub Selective Suspend Timeout)'
# Next section below is the Third GUID 'Power Setting GUID: 48e6b7a6-50f5-4782-a5d4-53bb8f07e226 (USB selective suspend setting)'
# These GUIDs will be used in the commands below
# These commands unhide the Power Hub Selective Suspend Time Out in the Power Plan USB Settings

# The first GUID is the Subgroup GUID: 2a737441-1930-4402-8d77-b2bebba308a3
# The second GUID is the Power Setting GUID: 0853a681-27c8-4100-a2fd-82013e970683
powercfg -attributes 2a737441-1930-4402-8d77-b2bebba308a3 0853a681-27c8-4100-a2fd-82013e970683 -ATTRIB_HIDE

# The first GUID is the Subgroup GUID: 2a737441-1930-4402-8d77-b2bebba308a3
# The thrid GUID is the Power Setting GUID: 48e6b7a6-50f5-4782-a5d4-53bb8f07e226
powercfg -attributes 2a737441-1930-4402-8d77-b2bebba308a3 48e6b7a6-50f5-4782-a5d4-53bb8f07e226 -ATTRIB_HIDE

# These commands Hub Selective Suspend Time Out to 0
# The first GUID is the Subgroup GUID: 2a737441-1930-4402-8d77-b2bebba308a3
# The second GUID is the Power Setting GUID: 0853a681-27c8-4100-a2fd-82013e970683
powercfg -setacvalueindex $cleanGuid 2a737441-1930-4402-8d77-b2bebba308a3 0853a681-27c8-4100-a2fd-82013e970683 0

# The first GUID is the Subgroup GUID: 2a737441-1930-4402-8d77-b2bebba308a3
# The thrid GUID is the Power Setting GUID: 48e6b7a6-50f5-4782-a5d4-53bb8f07e226
powercfg -setdcvalueindex $cleanGuid 2a737441-1930-4402-8d77-b2bebba308a3 48e6b7a6-50f5-4782-a5d4-53bb8f07e226 0

Write-Host "USB Selective Suspend Time out set to 0" -ForegroundColor Green
powercfg -setactive $cleanGuid

# 5. Disable "Allow the computer to turn off this device to save power" for all hardware
# This uses WMI to target the Power Management tab in Device Manager for all devices.
Get-CimInstance -Namespace "root\WMI" -ClassName "MSPower_DeviceEnable" | ForEach-Object {
  Set-CimInstance -InputObject $_ -Property @{Enable = $false} -ErrorAction SilentlyContinue
}
Write-Host "Disabled -- Allow the computer to turn off this device to save power for all hardware" -ForegroundColor Green
powercfg -setactive $cleanGuid

# 6. Unhide the 'Turn off hard disk after' setting in Power Options
# This ensures the command works even if the UI has hidden the disk settings.
powercfg -attributes SUB_DISK 6738e2c4-e8a5-4a42-b16a-3971e75a7627 -ATTRIB_HIDE
# Set the 'Turn off hard disk after' timeout to 0 (Never)
powercfg -setacvalueindex SCHEME_CURRENT SUB_DISK 6738e2c4-e8a5-4a42-b16a-e040e769756e 0
powercfg -setactive SCHEME_CURRENT

Write-Host "Hard disk power-down has been disabled (Set to 'Never')." -ForegroundColor Green
# 7. Disable Powerthrottling for VMware Workstation executable.
powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"
Write-Host "Disable Powerthrottling for VMware Workstation executable" -ForegroundColor Green
# 8. Apply changes immediately
powercfg -setactive SCHEME_CURRENT
Write-Host "All power-saving restrictions have been disabled." -ForegroundColor Green
Write-Host "`n...Changes Applied, Script Completed" -ForegroundColor Cyan

 

The Output:

Lastly, I make sure the correct power plan is active. I used the commands ‘powercfg -list’ to show the active plan and then ‘powercfg -setactive GUID’, replacing GUID with the plan I wanted.

Other Items:

Command to reset power plan to default: powercfg -restoredefaultschemes

Using PowerShell to setup AV exceptions for Workstation 25H2u1 and Windows 11

Posted on Updated on

Adding AV exceptions to your Workstation deployment on Windows 11 can really improve the overall performance. In this blog post I’ll share my exclusion script recently used on my environment.

NOTE: You cannot just cut, paste, and run the script below. There are parts of the script that have to be configured for the intended system.

What the script does.

  • For Windows 11 users with Microsoft’s Virus & threat protection enabled this script will tell AV to not scan specific file types, folders, and processes related to VMware Workstation.
  • It will ignore exceptions that already exist.
  • It will display appropriate messages (Successful, or Already Exists) as it completes tasks.

What is the risk?

  • Adding an exception (or exclusion) to antivirus (AV) software, while sometimes necessary for application functionality, significantly lowers the security posture of a device. The primary risk is creating a security blind spot where malicious code can be downloaded, stored, and executed without being detected.
  • Use at your own risk. This code is for my personal use.

What will the code do?

It will add several exclusions listed below.

  • File Type: Exclude these specific VMware file types from being scanned: 
    • .vmdk: Virtual machine disk files (the largest and most I/O intensive).
    • .vmem: Virtual machine paging/memory files.
    • .vmsn: Virtual machine snapshot files.
    • .vmsd: Metadata for snapshots.
    • .vmss: Suspended state files.
    • .lck: Disk consistency lock files.
    • .nvram: Virtual BIOS/firmware settings. 
  • Folder: Unique to my deployment it will exclude the following directories to prevent your antivirus from interfering with VM operations 
    • VMware Installation folder
    • VM Storage Folders: Exclude the main directory where I store my virtual machines.
    • Installation Folder: Exclude the VMware Workstation installation path ((default: C:\Program Files (x86)\VMware\VMware Workstation).
  • Process:
    • vmware.exe: The main Workstation interface.
    • vmware-vmx.exe: The core process that actually runs each virtual machine.
    • vmnat.exe: Handles virtual networking (NAT).
    • vmnetdhcp.exe: Handles DHCP for virtual networks.

The Script

Under the section ‘#1. Define your exclusions ‘ is where I adapted this code to match my environment

# Check for Administrator privileges
if (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
Write-Warning "Please run this script as an Administrator."
break
}

# 1. Define your exclusions

# This is where you put in YOUR folder exclusions
$folders = @("C:\Program Files (x86)\VMware\VMware Workstation", "D:\Virtual Machines", "F:\Virtual Machines", "G:\Virtual Machines", "H:\Virtual Machines", "I:\Virtual Machines", "J:\Virtual Machines", "K:\Virtual Machines", "L:\Virtual Machines")

# These are the common process exclusions

$processes = @("C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe", "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe", "C:\Program Files (x86)\VMware\VMware Workstation\vmnat.exe", "C:\Program Files (x86)\VMware\VMware Workstation\vmnetdhcp.exe")

# These are the common extension exclusions

$extensions = @(".vmdk", ".vmem", ".vmsd", ".vmss", ".lck", ".nvram")

# Retrieve current settings once for efficiency
$currentPrefs = Get-MpPreference
Write-Host "Checking and applying Windows Defender Exclusions..." -ForegroundColor Cyan

# --- Validate and Add Folders ---
foreach ($folder in $folders) {
if ($currentPrefs.ExclusionPath -contains $folder) {
Write-Host "Note: Folder exclusion already exists, skipping: $folder" -ForegroundColor Yellow
} else {
Add-MpPreference -ExclusionPath $folder
Write-Host "Successfully added folder: $folder" -ForegroundColor Green
}
}

# --- Validate and Add Processes ---
foreach ($proc in $processes) {
if ($currentPrefs.ExclusionProcess -contains $proc) {
Write-Host "Note: Process exclusion already exists, skipping: $proc" -ForegroundColor Yellow
} else {
Add-MpPreference -ExclusionProcess $proc
Write-Host "Successfully added process: $proc" -ForegroundColor Green
}
}

# --- Validate and Add Extensions ---
foreach ($ext in $extensions) {
if ($currentPrefs.ExclusionExtension -contains $ext) {
Write-Host "Note: Extension exclusion already exists, skipping: $ext" -ForegroundColor Yellow
} else {
Add-MpPreference -ExclusionExtension $ext
Write-Host "Successfully added extension: $ext" -ForegroundColor Green
}
}

Write-Host "`nAll exclusion checks complete." -ForegroundColor Cyan

The Output

In the output below, when the script creates an item successfully it will show in green. If it detects a duplicate it will output a message in yellow. I ran the script with a .vmdk exclusion already existing to test it out.

When its complete the AV exclusions in Windows should looks similar to the partial screenshot below.

To view the exclusions, in Win 11 open ‘Virus & Threat Protection’ > Manage Settings > Under Exclusions chose ‘Add or remove exclusion’

Upgrading Workstation 25H2 to 25Hu1

Posted on Updated on

Last February 26 2026 VMware released Workstation Pro 25H2u1. It’s an update that does repair a few bugs and security patches. In this blog I’ll cover how to upgrade it.

Helpful links

Meet the Requirements:

When installing/upgrading Workstation on Windows most folks seem to overlook the requirements for Workstation and just install the product. You can review the requirements here.

There are a couple of items folks commonly miss when installing Workstation.

  • The number one issue is Processor Requirements for Host Systems . It’s either they have a CPU that is not supported or they simply did not enable Virtualization support in the BIOS.
  • The second item is Microsoft Hyper-V enabled systems. Workstation supports a system with Hyper-V enabled but for the BEST performance its best to just disable these features.
  • Next, if you’ve upgraded your OS but never reinstall Workstation, then its advised to uninstall then install Workstation.
  • Lastly, if doing a fresh OS install ensuring drivers are updated and DirectX is at a supportable version.

How to download Workstation

Download the Workstation Pro 25H2u1 for Windows. Make sure you click on the ‘Terms and Conditions’ AND check the box. Only then can you click on the download icon.

Choose your install path

Before you do a fresh install:

If you are upgrading Workstation, review the following:

  • Ensure your environment is compatible with the requirements
  • If you have existing VMs:

Note: If you are upgrading the Windows OS or in the past have done a Windows Upgrade (Win 10 to 11), you must uninstall Workstation first, and then reinstall Workstation. More information here.

Upgrading Workstation 25H2 to 25Hu1

Run the download file, wait a min for it to confirm space requirements, then click Next

Accept the EULA.

Compatible setup check

Confirm install directory

Check for updates and join the CEIP program.

Allow it to create shortcuts

Click Upgrade to complete the upgrade

Click on Finish to complete the Wizard.

Lastly, check the version number of Workstation. Open Workstation > Help > About