Win Sandbox is enterprise and not activated

Hi Gang,

On my work laptop, I decided to upgrade from home to pro using an unused win 7 pro key that we had from a system that was trashed (client upgraded to a new PC)

I performed the upgrade, at which time rebooting my laptop decided it was enterprise and couldn't activate (even though it accepted the key to begin that process).

I went back through the activation process, entered the key again (it had not been used to upgrade anything) and after churning for a minute, my install is activated and is windows 10 pro. :)

I then checked in task manager, virtualization was enabled, and went to win features, whereas now as opposed to earlier (on home) I now had the win sandbox feature to enable, and I did so.

After it completed and I rebooted, I opened it, and immediately found I had no internet. I solved that issue as by adding the vadapter to my existing MS network bridge adapter and retrying, no problem there.

However the version of the sandbox shows as enterprise and not activated because it found no key.

Trying the "Default" pro key it just tells me it is wrong.

I'm wary of trying the same win 7 pro key used to upgrade my host system, lest that cause further issues, or would that be the solution at this juncture?

Thanks beforehand,

Marc (RWOne)

Update: On my home system running pro, seems the same ... so maybe not a bug?

Hi gang!

Well, being that I had upgraded this lappy to pro, I was stuck on it being something wrong... After seeing the same thing on my Home System and another 2 laptops running the IP builds and trying it, it does make sense that you wouldn't be running sandbox for longer than you need to.

I'm glad Superfly mentions the bug about enterprise after upgrading to pro, second time I've ran into that. Though this time on this laptop re-entering the win 7 key after the upgrade was completed got it ironed out.

Everyone have a great week!

Kari said:

No, it's not a bug. Sandbox shouldn't be, and is not activated.

Hi there
I agree in principle but then you can't test things like personalisation / different languages etc since Windows has to be activated to enable those features.

I like the idea of sandboxing but it needs to be a bit more fully implemented with more features and configuration options, possibly allow saving state of sandbox to HDD so you can use different test scenarios, allow save over re-boots so you can test software that needs a re-boot after install and the display language etc is only in US Eng.

BTW it also doesn't play well with VMWare products -- even if you disable the sandbox again then it's a devil's of an own job to get VMWare working again -- I just restored an image I'd taken prior to enabling sandbox -- quicker than messing around with obscure registry entries that don't always do what they are supposed to.

Windows Sandsbox needs to skip the whole activation thing if you need to test it properly with different configurations, programs etc etc. Or better it should already be permanently activated.

Incidentally you'll need a machine with decent I/O (preferably SSD's) and a decent powerful processor or you won't have a very good experience -- on poor HDD's and / or low power CPU's it runs like trying to row a boat in a stream of molasses.

Cheers
jimbo