ℹ️ Visual Studio Enterprise Edition support was provided in this fork which is now removed by the author: l3afblow3r/VSEELicense
⚠ Visual Studio Community 2022 seems to have no time limit, see this issue for details: #14 | VS 2022 support
PowerShell module to get and set the Visual Studio Community Edition license expiration date in the registry. Visual Studio 2013, 2015, 2017, and 2019 are supported.
Based on Dmitrii's answer to this Stack Overflow question: Visual Studio Community 2017 is a 30 day trial?
-
Download/clone this repository
-
Run
PowerShell.exeorpwsh.exeas the Administrator -
Import module:
Assuming that you cloned/downloaded this repo to
C:\VSCELicenseImport-Module -Name 'C:\VSCELicense\VSCELicense.psd1'
If you get
execution of scripts is disabled on this systemmessage, you can temporarily override PowerShell execution policy by runningSet-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
See PowerShell documentation for more details:
All supported versions of Visual Studio.
Get-VSCELicenseExpirationDateOne specific version of Visual Studio.
Get-VSCELicenseExpirationDate -Version 2017Multiple versions of Visual Studio.
Get-VSCELicenseExpirationDate -Version 2019, 2017⚡ Writing to the Visual Studio license registry key requires elevated permissions. Run PowerShell as administrator for examples to work.
All supported versions of Visual Studio.
Set-VSCELicenseExpirationDateOne specific version of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2017Multiple versions of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2019, 2017All supported versions of Visual Studio.
Set-VSCELicenseExpirationDate -AddDays 10One specific version of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2017 -AddDays 10Multiple versions of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2019, 2017 -AddDays 10⚡ This will immediately expire your license and you wouldn't be able to use Visual Studio.
All supported versions of Visual Studio.
Set-VSCELicenseExpirationDate -AddDays 0One specific version of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2017 -AddDays 0Multiple versions of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2019, 2017 -AddDays 0- 0.0.9 - Added VS 2013 support (@andreburto)
- 0.0.8 - Make it easier to use by not requiring to specify the Visual Studio version
- 0.0.7 - Added VS 2015 support (@GDI123)
- 0.0.6 - Load
System.Securityassembly if the 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 VS 2019 support
- 0.0.1 - Initial commit, VS 2017 support