Windows 8 Build 8056 with WORKING START SCREEN

[BetaNewbie]

Seeing is believing...
MetroFetro released a tookit named Metro Unlocker 1.0, It can unlock the Start Screen in Build 8056.

Well, charms, snap, picture password & PIN, and even Windows Live ID login are working.
I registered a secondary MS ID to test it...

MoGo... Yes, it is the codename of the Start Screen, confirmed.


Native 8056 version, of cause. Since 8102 can't do this.


Yes, Windows Live ID Login works.

[ovctvct]

Can you please PM me a link?(I won't share it, I promise) I can't believe it...

EDIT: found it: https://drive.google.com/file/d/0B-OLQy ... ef=2&pli=1 Is this really original 8056 metro? I somewhat doubt it's autencity, but I'll try check it myself.

I guess it includes 8056's shsxs.dll, and fixes the mo framework, which according to Lukas is broken in 8056. I extracted the file, seems it has some shsxs.dll dated aug 12th, 2011, without version, and some registry hacks. Looks legit atm. I've been waiting for this for years...

Edit 2: Tried it, looks exactly the same as the one Lukas posted(same build but other lab):
his build:


This one:

So shsxs.dll must be the 8056 one.

[beta.a.brian]

Was wondering how to do this for years

[DiskingRound]

Looks like today is the big day. But anyways, I think I've seen some shsxs.dll on some malware scanning website dated before August 23 of 2011, about a year ago. It was not available for download anywhere else and I don't remember where it is at the moment.

Offtopic Comment

It would be cool IMO if a build in the 8010-8040 range were to leak to have the blue-gray crossword wallpaper and to see if earlier versions of the start screen can be unlocked.

[Lukas Marsik]

You won't be able to "unlock" anything early with this. It's 8102's shsxs which on top of that seems to be reshacked (even though very lightly)

[Roo_the_Vickty]

Readme.txt says it all

[ovctvct]

You won't be able to "unlock" anything early with this. It's 8102's shsxs which on top of that seems to be reshacked (even though very lightly)

But why would it be dated as 12-aug-2011 then?

[Lukas Marsik]

The timestamp in the DLL's file header matches to the one you can find in WDP which is: 1313195550 -> Sat, 13 Aug 2011 01:32:30 GMT
Besides that, all tables except .rsrc and .reloc are identical.

[ovctvct]

@Lukas why is there no immersive IE in this build? 7989 and older 79xx builds already had it, but this one doesn't.
And there looks like I have found the shutdown bug in 8056 while logoff/shutdown- a BSOD appears.

[Lukas Marsik]

Immersive IE is there, it won't work with 8102's shsxs

[yourepicfailure]

And if you folks look closely at the video date, it was released in January 2016.
Not exactly "new".

[ovctvct]

Can 8102 apps be somehow installed on this? I tried copying an 8102 demo app to 8056, as well as importing it's registry keys from 8102, but it doesn't appear on the start screen. Anything I am missing?

[beta.a.brian]

For some reason control panel doesn't work for me

[Windows OS]

To quote M. Bison:
YES!!! YES!!!
It finally happened. A build of Windows 8 done before the Developer Preview with the Start Screen (well, more like hacked in to an already leaked build, but still). I'm gonna try it on a install of 8056 soon.

Can 8102 apps be somehow installed on this? I tried copying an 8102 demo app to 8056, as well as importing it's registry keys from 8102, but it doesn't appear on the start screen. Anything I am missing?

Maybe repackaging 8102's apps as Appx files and installing them onto 8056 could get it to work.

You won't be able to "unlock" anything early with this. It's 8102's shsxs which on top of that seems to be reshacked (even though very lightly)

Hmm... Could anyone try to use the 8102 shsxs.dll file and see what'll happen (reshacked or not)?

UPDATE: I was playing around with the Settings app and I found a link that says "Install the latest version of Windows" (emphasis on image added by me):

What happens when I click it brings up a weird instance of Internet Explorer, that looks like the immersive version stuck in a window with the desktop version's context menus:


UPDATE 2: I decided to create another account, and it appears that Windows attempted to use the accent from the Developer Preview on the Start screen, but it's a bit broken:

[Lukas Marsik]

You won't be able to "unlock" anything early with this. It's 8102's shsxs which on top of that seems to be reshacked (even though very lightly)

Hmm... Could anyone try to use the 8102 shsxs.dll file and see what'll happen (reshacked or not)?

I don't think you understand what I said. This "unlocker" uses 8102's shsxs. That's why some things fail or look out of place.

[ovctvct]

He probably meant to run the non-reshacked one, this one is slightly reshacked.
Anyway, notice how the charm bar is different from 8102's(you need to press win+shift+c to open it):


Sadly I cant make it "genuine" to unlock those settings.. The video poster shown those options unlocked, how exactly IDK.

[Courage]

If you want a color other than purple for the Start Screen without it glitching out, this is what you have to do:

1. Install 8056 as normal.
2. During OOBE, create a dummy user account.
3. Download and use Redpill Enabler. (I don't know if this is necessary, but do it just in case.)
4. Run Windows/System32/oobe/msoobe.exe and go through the steps, including choosing your colour and creating your desired user account.
5. Restart and login into your new account. Delete the dummy one if you want.
6. Run Metro Enabler.

Result:

[awesomeguy]

Please PM me the link.

[Lukas Marsik]

Please PM me the link.

It's in the first reply.