Skip to main content

TeamViewer Commercial Use Suspected / Detected / Blocked / Trial Expired (Solved)

 

·         Write down you TeamViewer id somewhere so we will check later on it

·         Uninstall TeamViewer

·         Click Start then type %appdata% – now delete the TeamViewer folder

 

·         Click Start the type %temp% and delete the contents of this folder as well as the

 

·         Click Start then type regedit, delete the registry folder at HKEY_CURRENT_USER\Software\TeamViewer & HKEY_LOCAL_MACHINE\SOFTWARE\TeamViewer if any


·       Search every key related to TeamViewer with the help of search (F3) again and again until all the registry keys deleted.

 

·         Now change your MAC address, either manually or with a tool like TMAC [I suggest changing the MAC address on both network connections, i.e. wireless and LAN]

·         Restart you pc and install TeamViewer again. You will see your iD is changed

 

 

https://www.youtube.com/watch?v=GQTPMI7rfBc


Comments

Post a Comment

Popular posts from this blog

You Can’t Access This Shared Folder Because Your Organization’s Security Policies Block Unauthenticated Guest Access

  You Can’t Access This Shared Folder Because Your Organization’s Security Policies Block Unauthenticated Guest Access     When trying to access from new server to old shares you might get this error : ” You can’t access this shared folder because your organization’s security policies block unauthenticated guest access. These polices help to protect you PC from unsafe or malicious devices on the network”.   you need to allow insecure guest logon : Default registry value: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] "AllowInsecureGuestAuth"=dword:0 Configured registry value: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] "AllowInsecureGuestAuth"=dword:1 Or through group policy: Navigated to  Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation  and selected the  Enable insecure guest logons  
Post a Comment
Read more