Archive

Archive for the ‘Insider preview windows 10’ Category

Some Settings are Hidden and Managed by Your Organization

April 7, 2018 Leave a comment

Let me have access fully to my computer LOL, wtf MS please. If you like me had a nice brand new laptop with windows 8 installed but even tho it was fully legit I had a key that could not be upgraded for FREE. So I jumped in and used the insider program and all was good but around 18 months ago, I got the windows needs activating message.

We found a cure for that via LMGTFY, this time I needed to alter some settings and got the headline message again, it needs fixing this is the best method I found on the GOOGLE, so as always I’m sharing the love. HERE (Like if helps)

WORKED FOR ME 🙂  the joy of free and easy

Advertisements

Annoying windows 10 updates!!

March 26, 2017 Leave a comment

I’ve been running windows 10 insider progam since it was released a long time ago, it’s much improved on win8. but I was lucky enough to upgrade via the 8 purchase due to my license not working even tho I paid for it unlike some.

Anyway this is about disabling updates, very simple hit the win + R and type in – gpedit.msc

and rid yourself of the damn updates every other day.

Screenshot (2)

Activation Issue With Windows 10 Technical Preview for Enterprise

January 30, 2015 Leave a comment

Another key change JULY 2015 –  REMEMBER INSIDER ENDS 1ST OCTOBER 😦

LATEST: CKFK9-QNGF2-D34FM-99QX2-8XC4K

Latest build Monday 20th July 2015 key is playing up 🙂 stay tuned !!!! 

Update 1st May 2015 – moved on to enterprise insider preview activation code has changed

GO HERE VTNMT-2FMYP-QCY43-QR9VK-WTVCK

Jan 30th 2015 – I just used the key you supplied as. Slui3 doesn’t work on my system

Cheers for sharing

mceworld

Problem:

I have installed Windows 10 technical preview,but activation is not accepted.

Resolution:

You don’t need to activate the Technical Preview – it’s activated automatically.The product key provided by Microsoft for Windows 10 Technical Preview for Enterprise is PBHCJ-Q2NYD-2PX34-T2TD6-233PK which is required for recovery scenarios.

To fix the issue:

1.] Open Command Prompt with Administrative privileges.

2.] Type: SLUI 3

3.] Enter  the product key PBHCJ-Q2NYD-2PX34-T2TD6-233PK

View original post