Microsoft Surface Pro IssueSolved

Hi Aldo,

It's not a solution but maybe you can check if Hyper-V is activated on the Surface pro, and in so doing Hypervisor. (You can make a search "Windows 8.1 Hypervisor" and find interesting articles, like: http://blogs.technet.com/b/canitpro/archive/2014/03/11/step-by-step-enabling-hyper-v-for-use-on-windows-8-1.aspx)

Best regards,Alexandre Leclerc

Good morning,Any update/solution to this?We've just tried a Surface Pro too and it's tripping the Hyper-V error.Note: checked whether Hyper-V is installed, and it's not.Tried: bcdedit /set hypervisorlaunchtype off (from admin command prompt) {needs reboot}That didn't work.

This is a bit of a pain 🙁 - the Surface Pro was going to demo to a customer...

Any ideas please?

Under some rare cases TurboActivate 3.4.4 falsely detects a machine as a VM if VM software is installed on the computer (like VirtualBox or VMware Workstation). Do they have "host" VM software installed?

By the way, this won't be a problem in the next version of TurboActivate.

Good morning,

This is an "out of the box" Surface Pro 3; then VS 2013 installed. No deliberate installation of VM software (and VS 2013 doesn't include device building, just .NET Winforms). If you can let us know what to look for we can tell you whether it's there.

So - not sure what's causing the issue.

Short-term solution - allow VMs... I guess.

When (guestimate) is the next version of TurboActivate? (need to determine what "short term" is)

Thanks,

Michael Dye.

The new TurboActivate is coming out later this week.

We have a few surface pros hanging around here, and we'll try to reproduce this on one of them.

We've found the bug, fixed it, and it will be solved with the next version.

Thanks Wyatt,

Good news - I came across another user on a Surface Pro 2 with the same issue and he'd done the same (allow VMs) as his work around.

I *think* we have to remember to download the new version of TurboActivate? I can't get notifications to work on this forum (probably not clicking somewhere I should) - is there an email notification about updates?

Or a rough time frame and I'll remember to check back?

Thanks,

Michael Dye.

Yeah, this forum software is crappy. The new version should be out next week. You'll be able to download it on your API page.

This is fixed in TurboActivate 3.4.6 -- out now.

We are using TurboActivate 3.4.6, but statically linked, and we are still having these VM issues in Surface Pro 3s - are we doing something wrong?

Is Hyper-V enabled on the machine? If so, then the machine *is* a VM (because of the way Hyper-V works the "host" machine is still running as a virtual machine).

Do you know how to check if Hyper-V is enabled? Go to "Programs and Features" in the control panel and click "Turn Windows features on or off". Then uncheck "Hyper-V", press OK, and after it goes through the wizard it will ask you to restart your computer. Do that. Then TurboActivate will detect the computer as a real computer.

We have an app, VMs not allowed, but it won't retain its activation on a Surface Pro. The Surface Pro is running Windows 10, Hyper-V is not installed. The Turboactivate we are using is 3.4.6.

Whenever the user starts our product, it says "Not activated". You click Activate, then click "Activate ISIS online now" and it activates ok. You then need to refresh the licence manually to make it read all the allowed options. Then it works properly. Until the user turns the app off and starts again. I've tried running our product as Admin, and running Turboactivate as Admin. Does anyone have any other ideas to try?

Much more information is needed. Code samples. A way to reproduce it.

My guess is that the user is using some sort of "cleaning" app, that is cleaning what it perceives are "junk files" (which are really the activation data files).

Also, make sure you use TA_SYSTEM (which is the smartest option on Windows).

Here is the function:

Sub CheckLimeTrial(ByVal bShow As Boolean) TurboActivate.VersionGUID =

Dim gr As New IsGenuineResult

Try ' Check if we're activated, and every 90 days verify it with the ' activation servers. In this example we won't show an error if ' the activation was done offline. (see the 3rd parameter of ' the IsGenuine() function) gr = TurboActivate.IsGenuine(14, 7, True, True) '14,3 from families '90,14 If gr = IsGenuineResult.InternetError Then Dim sMsg As String = ... MessageBox.Show(sMsg) ElseIf gr = IsGenuineResult.NotGenuine Then Try If TurboActivate.IsActivated Then gr = TurboActivate.IsGenuine If gr <> IsGenuineResult.Genuine Then MessageBox.Show(...) End End If End If Catch End Try End If IsLimeActivated = (gr = IsGenuineResult.Genuine _ OrElse gr = IsGenuineResult.GenuineFeaturesChanged _ OrElse gr = IsGenuineResult.InternetError) Catch ex As TurboActivateException MessageBox.Show("Failed to check if activated: " + ex.Message) End Try

If Not IsLimeActivated Then TurboActivate.UseTrial(TurboActivate.TA_Flags.TA_USER) If bShow Then Dim f As New frmTrial f.ShowDialog() End If End If End Sub

I've watched it happen - you run the product, it says unactivated, you activate it, close it down and start it again and it says unactivated again. I couldn't see any cleaning utilities running and I can't see that anything has the opportunity to clean junk files.

What is the benefit of TA_SYSTEM over TA_USER?

This is a problem in your code. You're swallowing exceptions. Don't do that. If you swallow exceptions you never know when a problem happens.

Where am I swallowing exceptions? As far as I can see, the whole routine is wrapped in a try statement.

What exceptions should I be looKing for, or might cause this behaviour on a Surface pro?

What is the benefit of TA_SYSTEM over TA_USER?

Everything inside the ElseIf gr = IsGenuineResult.NotGenuine Then is inside a try block which is swallowing exceptions.

You need to give me a lot more information. What happens when you run TurboActivate.exe? Does it say you're still activated?

>> "What is the benefit of TA_SYSTEM over TA_USER?"

TA_SYSTEM stores files on a system level rather than a per-user level. Among other things, this means "helper applications" are less likely to mess with the files (i.e. "clean them up").

Sorry, yes I see that. The swallowed exception is when the IsGenuine call returns NotGenuine. Obviously I have assumed NotGenuine means it is just not a genuine installation and so I missed a possible exception there. It looks like I shall have to produce a special version for this user with a catch at this point, to try and feed back to me what is happening, so I'd like to cover all bases. Without a surface pro I can't test this. Any suggestions what it might throw or what I might be looking for? Obviously I can't make one change, get the user to test it, then make another, etc, so I'd like to produce something which tells me exactly what the problem is. Would changing to TA_SYSTEM be the first step or should we leave that so we can find out what the problem is?

Whenever the user starts our product, it tells them "Not activated" in our own dialogue. They click Activate (which starts TurboActivate.exe), then they are offered a range of options. Click "Activate ISIS online now" and it activates ok. It must retain the activation key somewhere as we don't need to retype it. It doesn't affect the number of activations the user has in our Lime interface.

Thanks, Wyatt, Your patience is appreciatedNeil

>> "Would changing to TA_SYSTEM be the first step or should we leave that so we can find out what the problem is?"

I'd do that first. Also, make sure the customer isn't disabling / enabling network adapters. They might not be giving you the whole story.

In TurboActivate 4.0 (out soon) we handle cases where the customer disable network adapters. In prior versions, TurboActivate just sees the computer as different.

>> "Without a surface pro I can't test this."

We have multiple surface pros and we can't reproduce what the customer is experiencing.

Thanks, I'll try and remote in and check what she has, and try that change.