[DISCUSSION] Windows 10 Pro for Workstations SKU

So WHEN will be able to finally use updates with this Windows for Workstations? I'm kinda worried about Meltdown/Spectre bugs...

 

As it looks atm with RS4 release.

 

There are no official ProfessionalWorkstation installation media released yet

 

Damn,I knew it....we must wait some more.

 

Ok, put myself on the fast ring.. tracked down UUP to ISO (thanks to @abbodi1406) and now I'm waiting for something to happen. Assuming the updated get downloaded, and If the ISO generated by UUP>ISO for 17063 can only have the edition which was downloaded (ie, the latest changes to the currently activated edition), and I'm running 16299 PROfW, is there a chance I end up with a ProfW version of the ISO? Anyway, one hell of a rabbit hole. I'll come back tomorrow and see if the update has downloaded.

 

You probably will download the home or pro uup file set, if you get anything.

 

PfW (like Ent and other SKUs) can be upgraded with that Home/Pro ISO.

 

When 16299.15 was released i did test the 16299.15 pro-ws fast ring thing, the uup set it downloaded was pro (iirc), so the iso created from it will be pro, not pro-ws.

I replied on this:

 

I know. Still the upgrade using the mounted ISO will work .

 

He expects to end up with a ready made pro-ws 17063 iso by converting, the downloaded by WU, uup files, there is no edition specific pro-ws esd file so he'll end up with a pro iso.

 

You need to login to view this posts content.

 

Code:

[OSINF] Edition {CBS} : Professional

The CBS version is missing in your new test. I don't know what that means, but it seems significant. I've been watching for discrepancies between the Registry version and the CBS version, but I'm starting to think it doesn't really matter.

Is is likely that the difference between PRO and PROWS is purely policy?

 

My "new" test is with the old 16299.15 UUP Showcase iso i made when 16299.15 still only was available by UUP, it has MRP67 onboard, pro-ws is a dism offline set-edition-ed version.

 

Just for fun, on Hyper-V, I installed a 16278 ProWS made with @GodHand 's tool using the Core ISO. I mounted it first, and injected the retail product key obtained from product.ini of the same ISO. It was activated. Once installed I used gatherosstate.exe, and obtained the GenuineTicket.xml. Then I mounted the install.wim from a 17063 ProWS I had made earlier. I put the GenuineTicket.xml into the mounted image in this folder: ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket. Then I saved, unmounted, created ISO, and installed in Hyper-V. This time I found that my install was Digitally Activated! Of course from this point it can be tied to a MS Account as I have done, and this is the OS I am using on my Main Drive.
So this is still possible, and build 16278 may be more easily obtained. I obtained this copy with @mkuba50 's UUP tool.

 

I always use the wimgapi.dll in PowerShell wrappers and assigned to the proper system namespace. You can do absolutely anything that way.

Code:

        [DllImport("Wimgapi.dll", CharSet = CharSet.Unicode, SetLastError = true, EntryPoint = "GAPIWIMACTIVATE)]
        [return: MarshalAs(UnmanagedType.Bool)]
        internal static extern bool
        GAPIWIMACTIVATE
        (
            [In]        SafeHandle Handle,
            [Out]   out StringBuilder ImageInfo,
            [Out]   out uint SizeOfStringInfo
        );

etc...

 

You need to login to view this posts content.

 

Any more on that method?

 

GodHand, does that include applying a package without the need of signature check? (I don't know computer language. Thank you.)

Edit: I see now. Thank you.

 

You need to login to view this posts content.