- Remove Terminal Server licenses from an RDP client
- Summary
- Clean RDP client’s license cache
- Did this fix the problem
- Удаление лицензий терминала Server у клиента RDP
- Аннотация
- Чистый кэш лицензии клиента RDP
- Исправлена ли эта проблема
- remove software licensing notification windows 7
- Uninstall Microsoft product trial license or KMS license completely
- Steps to remove your Office license
- Steps to remove your Windows license
- Leave a Reply Cancel reply
- 84 thoughts on “ Uninstall Microsoft product trial license or KMS license completely ”
Remove Terminal Server licenses from an RDP client
This article describes how to remove Terminal Server licenses from a Remote Desktop Protocol (RDP) client.
Original product version: В Windows 10 — all editions, Windows Server 2012 R2
Original KB number: В 187614
Summary
When an unlicensed client connects to a Terminal Server for the first time, the Terminal Server issues the client a temporary Terminal Server Client Access License (CAL) token. After the user has logged into the session, the Terminal Server instructs the License Server to mark the issued temporary Terminal Server CAL token as being validated. The next time the client connects, an attempt is made to upgrade the validated temporary Terminal Server CAL token to a full Terminal Server CAL token. If no license tokens are available, the temporary Terminal Server CAL token will continue to function for 90 days. The license is stored in the client’s registry.
32-bit RDP clients store their license under the key HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing .
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
Clean RDP client’s license cache
To clean the client’s license cache, just delete this key and its subkeys. The next time the client connects to the server, it will obtain another license.
For 16-bit RDP clients, run regedit /v . Then delete the keys under \Software\Microsoft\MSLicensing to clean the client’s license cache. You can also delete the BIN files from \Windows\System\Regdata .
The RDP client for Macintosh stores the license in a file on the local computer in the folder hierarchy under /users/Shared/Microsoft/RDC Crucial Server Information/ . To clean the Macintosh client’s license cache, delete the contents of this folder. The client will try to obtain a new license from the server the next time that it connects.
If you delete the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing subkey on a client that is running Windows Vista or a later version, later attempts to connect to a Terminal Server may fail. Also, you receive the following error message:
An Error occurred in the Licensing Protocol
To resolve this problem, right-click the Remote Desktop Connection shortcut, and then select Run as Administrator. By default, the remote desktop connection runs as a user with the lowest user permissions. By default, a restricted user doesn’t have permission to write registry entries to HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys.
Did this fix the problem
Check whether the problem is fixed. If the problem isn’t fixed, contact support.
Удаление лицензий терминала Server у клиента RDP
В этой статье описывается, как удалить лицензии терминала Server из клиента удаленного протокола рабочего стола (RDP).
Оригинальная версия продукта: Windows 10 — все выпуски, Windows Server 2012 R2
Исходный номер КБ: 187614
Аннотация
Когда нелицензионный клиент впервые подключается к терминаловому серверу, сервер терминала выдает клиенту маркер временной лицензии клиентского доступа к терминалу сервера (CAL). После входа пользователя в сеанс сервер терминала поручит серверу лицензии отметить выданный временный маркер Cal Terminal Server как проверяемый. При следующем подключении клиента будет предпринята попытка обновить проверенный временный маркер CAL терминала Server до полного маркера Cal Terminal Server. Если нет токенов лицензии, временный маркер Cal Terminal Server будет работать в течение 90 дней. Лицензия хранится в реестре клиента.
32-битные клиенты RDP хранят лицензию под ключом HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing .
В этот раздел, описание метода или задачи включены действия, содержащие указания по изменению параметров реестра. Однако неправильное изменение параметров реестра может привести к возникновению серьезных проблем. Поэтому следует в точности выполнять приведенные инструкции. Для дополнительной защиты создайте резервную копию реестра, прежде чем редактировать его. Так вы сможете восстановить реестр, если возникнет проблема. Дополнительные сведения о том, как создать и восстановить реестр, см. в этой информации, как создать и восстановить реестр в Windows.
Чистый кэш лицензии клиента RDP
Чтобы очистить кэш лицензии клиента, просто удалите этот ключ и его подки. При следующем подключении клиента к серверу будет получена другая лицензия.
Для 16-битных клиентов RDP запустите regedit /v . Затем удалите ключи, \Software\Microsoft\MSLicensing чтобы очистить кэш лицензии клиента. Вы также можете удалить файлы BIN из \Windows\System\Regdata .
Клиент RDP для Macintosh сохраняет лицензию в файле на локальном компьютере в иерархии папок под /users/Shared/Microsoft/RDC Crucial Server Information/ . Чтобы очистить кэш лицензии клиента Macintosh, удалите содержимое этой папки. Клиент будет пытаться получить новую лицензию с сервера в следующий раз, когда он подключается.
Если удалить подкоть клиента с Windows Vista или более поздней версией, более поздние попытки подключения к терминалу могут привести к HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing сбой. Кроме того, вы получаете следующее сообщение об ошибке:
Ошибка произошла в протоколе лицензирования
Чтобы устранить эту проблему, щелкните правой кнопкой мыши ярлык удаленное подключение к рабочему столу, а затем выберите Выполнить в качестве администратора. По умолчанию удаленное подключение к рабочему столу выполняется как пользователь с самыми низкими разрешениями пользователя. По умолчанию ограниченный пользователь не имеет разрешения на запись записей реестра для HKEY_LOCAL_MACHINE. Поэтому попытки переписать ключ не MSLicensing удается. Запуск удаленного подключения к рабочему столу с административными учетными данными предоставляет разрешения, необходимые для записи необходимых ключей реестра.
Исправлена ли эта проблема
Проверьте, устранена ли проблема. Если проблема не устранена, обратитесь в службу поддержки.
remove software licensing notification windows 7
The popup is «titled software licensing» and comes up when i enter the control panel or any other windows program. It also states, «This computer is not running genuine window, To use this feature without interruption, this computer needs to be running genuine Windows. With genuine Windows you have access to all Windows updates and can be confident that your Windows software has the latest security and reliability enhancements from Microsoft.»
First let me start by saying my copy of windows is genuine. I bought this laptop brand new and I have the windows 7 home sticker on the bottom. Secondly let me point out that I have advanced A+, Cisco and programming skills. Now, I have disabled all annoying windows services and security threats that open ports on my computer; including windows updates and windows genuine software checker, remote access, fax services etc. I have almost rid my computer of all your annoying bloatware and cut your servers access to my computer entirely.
That is, with the exception of this notification and one in my task bar called «solve PC issues: 1 important message».
I thought I tracked the source of the annoying popups down to a dll file and after painstakingly getting the permissions to change system files; I changed the name of it to no avail. Please just point me to a registry file to delete/edit; or the executable that I can delete. After owning a computer store for years, I am not calling to verify my copy; nor am i turning your genuine «we don’t trust you» program back on so your servers can probe and open up ports for hackers to access. Nor am I downloading anything.
With that in mind, please stop annoying honest customers and tell me the source of the executable; I don’t want to waste any more hours of my life removing bloatware. Also don’t feed me, «automatic updates protects your computer» tech garbage that the average customer eats up. That may be true for the average Joe; but any advanced user knows it only opens vulnerabilities in the network.
Uninstall Microsoft product trial license or KMS license completely
As you know, the new Microsoft product installation usually includes a 30-days free trial license. However, the problem here is that the trial license is not uninstalled automatically when it is expired. And so this leads to the paradox that it keeps saying “Most features are disabled” or “Windows is not activated” even after activating it using a valid license. Besides, some of you guys who have ever used KMS license to activate your Windows or your Office and now you just want to remove it in order to use another product key. This is similar to the problem I just mentioned. And to address these issues, please do the following steps.
Steps to remove your Office license
Step 2:В Copy/run this command to determine what is the license key you want to remove.
If you see an error, try this command.
Note: “Office16” is codename of Office 2016. If you are using Office 2010/2013, replace “Office16” with “Office14” or “Office15”.
Determine license you want to remove
Step 3: Copy and run these commands to remove the license. Note: replace “VMFTK” with the last 5 characters of your product key.
If you see an error, try this command.
Office product key is uninstalled successfully
Steps to remove your Windows license
Step 2:В Execute this command.
Windows product key is removed successfully
Done! The license you want to remove is uninstalled successfully.
If you would have any questions or concerns, please leave your comments. I would be glad to explain in more details. Thank you so much for all your feedback and support!
Who am I ?
I am Guang, a third year college student. I’m currently managing two channels (Next Level ‘n’ Always Smile).
Leave a Reply Cancel reply
84 thoughts on “ Uninstall Microsoft product trial license or KMS license completely ”
O*G thank you so much! I’d installed a KMS license to use Office 2019 for free, but after some time it started having problems, so I bought Office 365. The problem was that I couldn’t make it work because the f*****g fake license was still there, somewhere. Now the original version is working, thanks a lot!
Thank you so much Mr. Guang, among so many suggestions in google your information is correct and help me to uninstall licence
Hello, wanted to remove the windows licenses but got this error:
Error: 0xC0000022 On a computer running Microsoft Windows non-core edition, run ‘slui.exe 0x2a 0xC0000022’ to display the error text.
Any work around how to fix this please? Need help so I can activate my windows.
HEY MATE!
PLEASE UPDATE YOUR INSTRUCTIONS FOR OFFICE 365 & 2019!
ASK VISITORS TO CLICK THEIR VERSION FIRST, THEN LINK DOWN THE PAGE TO #2016 #2019 #365 etc.
OR HAVE EXPANDABLE / COLLAPSABLE SECTIONS FOR EACH EDITION рџЂ =)
KEEP UP THE GREAT WORK! рџ––рџ¤рџ‘ЌрџЉрџЋрџ‡рџ¤©
WHAT IS THE CORRECT MICROSOFT OFFICE INSTALLATION PATH? WHERE IS OFFICE CLICK-TO-RUN C2R INSTALLED? WHERE IS MY OFFICE LOCATED?
THE CORRECT OFFICE & OFFICE 365 INSTALLATION PATHS! I HOPE THIS HELPS YOUR рџ‡рџ™ЏрџЋ
Office 365
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office\root\Office16\
-В» x64 64bit: C:\Program Files\Microsoft Office\root\Office16\ (rarely used due to Outlook and Office x64 Plugin incompatibility)
Click-To-Run (C2R)
-В» C:\Program Files\Common Files\Microsoft Shared\ClickToRun\
…?
Office 2019 (. )
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office\Office16\
-В» x64 64bit: C:\Program Files\Microsoft Office\Office16\ (rarely used due to Outlook and Office x64 Plugin incompatibility)
Click-To-Run (C2R)
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office 16\ClientX86\Root\Office16\
-В» x64 64bit: C:\Program Files\Microsoft Office 16\ClientX64\Root\Office16\
Office 2016
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office\Office16\
-В» x64 64bit: C:\Program Files\Microsoft Office\Office16\ (rarely used due to Outlook and Office x64 Plugin incompatibility)
Office 2016 Click-To-Run (C2R)
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office 16\ClientX86\Root\Office16\
-В» x64 64bit: C:\Program Files\Microsoft Office 16\ClientX64\Root\Office16\
Office 2013
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office\Office15\
-В» x64 64bit: C:\Program Files\Microsoft Office\Office15\ (rarely used due to Outlook and Office x64 Plugin incompatibility)
Office 2013 Click-To-Run (C2R)
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office 15\ClientX86\Root\Office15\
-В» x64 64bit: C:\Program Files\Microsoft Office 15\ClientX64\Root\Office15\
Office 2010
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office\Office14\
-В» x64 64bit: C:\Program Files\Microsoft Office\Office14\ (rarely used due to Outlook and Office x64 Plugin incompatibility)
Office 2010 Click-To-Run (C2R)
-В» x86 32bit: C:\Program Files (x86)\Microsoft Office 14\ClientX86\Root\Office14\
-В» x64 64bit: C:\Program Files\Microsoft Office 14\ClientX64\Root\Office14\
should i delete the one with the grace edition or kms client edition? thank you
Thank you very much for this article!
I needed to remove the fake non-genuine install from a computer and install a real license and this did the trick.
The genuine install kept asking for a the non-genuine license activation!
it was bazaar!
After removing the unlicensed copy per your instructions, all worked well!
anyone got an idea on how to do this with office on macOS?
KMs method only work with PC.
Hi guys вєпёЏ,
Can anyone help me?
I run the command given by msguides to activate windows 10, after I wanted to unactivate it due to security reasons, I then run the command given by msguides to uninstall ksm activation but after 4-5 day my windows got activated again this thing happens to me 5 times I keep on unactivating my windows it automatically get activated please help me to permanently unactivate my windows. рџ™Џрџ™Џ
You will find method to delete it completely.
@KWONG Perhaps think about other elements in OS that are triggering cached re-activation. e.g. Scheduled Tasks not removed, plus services that can be manually Stopped.
What are the exact names of the scheduled tasks created by your script? рџ™Џрџ‡
I’m having the same problem and can’t install a genuine key. Pls help, I’m not sure how this image is supposed to help.
I also have the same problem, it always activates again рџ™Ѓ
got any solution?
NEED TO REMOVE ALL ACTIVATION-RELATED SCHEDULED TASKS CREATED BY MSGUIDE’S SCRIPT. 🕵️‍♂️
ASK @KWONG WHICH TASKS NEED TO BE REMOVED! рџ¤ђ
NEED TO REMOVE ALL ACTIVATION-RELATED SCHEDULED TASKS CREATED BY MSGUIDE’S SCRIPT. 🕵️‍♂️
ASK @KWONG WHICH TASKS NEED TO BE REMOVED! рџ¤ђ
NEED TO REMOVE ALL ACTIVATION-RELATED SCHEDULED TASKS CREATED BY MSGUIDE’S SCRIPT. 🕵️‍♂️
ASK @KWONG WHICH TASKS NEED TO BE REMOVED! рџ¤ђ
THANKS A LOT GUANG!
Dear Guang,
Hi. How are you?
Office 2010. OfficeProPlus-KMS_Client edition. I cannot remove office product key. It says
ERROR CODE: 0xC004F025
ERROR DESCRIPTION: The Software Licensing Service reported that the action requires administrator privilege. Please help me to solve this issue.
Thanks,
Rivon
You have to run CMD as administrator, on an administator account
O*G. This was great, thank you, BUT you should NOT have the last one about removing the WINDOWS KEY so close to the other tutorial. I RAN THE COMMAND THINKING IT WAS STILL PART OF THE SAME OFFICE KEY REMOVAL GUIDE. Thank goodness it said: input error cannot find ….script.
Thank you for the first portion, though. Worked like a charm.