📜 VSEELicense

• Details
• Usage
• Examples
  • Get Visual Studio 2022 Enterprise Edition license expiration date
  • Set Visual Studio 2022 Enterprise Edition license expiration date
    • Set license expiration date to 31 day from now
    • Set license expiration date to 10 days from now
    • Set license expiration date to current date
• Changelog

Details

PowerShell module to get and set Visual Studio 2022 Enterprise Edition license expiration date in the registry.

Based on Dmitrii's answer to this question: Is Visual Studio Community a 30 day trial?

Usage

1. Download/clone this repository

2. Run PowerShell.exe as Administrator

3. Import module:

   Assuming that you cloned/downloaded this repo to C:\VSEELicense

   Import-Module -Name "C:\VSEELicense\VSEELicense.psd1"

   If you get execution of scripts is disabled on this system message, you can temporarily override PowerShell execution policy by running

   Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process

   See PowerShell documentation for more details:

   • Set-ExecutionPolicy
   • About Execution Policies

Examples

Get Visual Studio 2022 Enterprise Edition license expiration date

Get-VSEELicenseExpirationDate

Set Visual Studio 2022 Enterprise Edition license expiration date

⚡ Writing to the Visual Studio license registry key requires elevated permissions. Run PowerShell as administrator for examples to work.

Set license expiration date to 31 day from now

Set-VSEELicenseExpirationDate

Set license expiration date to 10 days from now

Set-VSEELicenseExpirationDate -AddDays 10

Set license expiration date to current date

⚡ This will immediately expire your license and you wouldn't be able to use Visual Studio.

Set-VSEELicenseExpirationDate -AddDays 0

Changelog

• 0.0.10 - Replaced 2019 with 2022 prerelase
• 0.0.9 - Added 2019 Enterprise support only. Removed 2015, 2017 & 2019 Community
• 0.0.8 - Make it easier to use by not requiring to specify Visual Studio version
• 0.0.7 - Added 2015 support (@GDI123)
• 0.0.6 - Load System.Security assembly if module was imported without manifest
• 0.0.5 - Duh, actually set PowerShellVersion = "3.0" in manifest
• 0.0.4 - Support downlevel PowerShell versions, starting from 3.0
• 0.0.3 - Fixed manifest to avoid execution errors under fresh PowerShell environments (@1Dimitri)
• 0.0.2 - Added 2019 support
• 0.0.1 - Initial commit, 2017 support