Open the iso where you got the install.wim from and replace the old install.wim with the new install.wim, and save the iso.
Nice s1ave77, ISO created with sucess, with .exe method of GodHand and tips of lomticksoftoast and Enthousiast. Now, time to install. Thanks pals!
@GodHand Code: .EXAMPLE .\ConvertTo-PfW.ps1 -SourcePath "D:\install.wim" .\ConvertTo-PfW.ps1 -SourcePath "E:\Windows Images\Win10_1709_English_x64_ALL.iso" Tried it out & it worked fine. Is it possible for you to add a destination as well? ie: Code: .\ConvertTo-PfW.ps1 -SourcePath "D:\install.wim" -DestinationPath "D:\ProWS.wim" I'd do it myself but am unfamiliar with Powershell (note I should learn it).
A destination other than the desktop? Yeah that can be implemented. And PowerShell has so many uses and abilities it's fantastic, particularly when you write advanced functions/modules that utilize the Windows APIs and use the .NET Framework to allow scripts to use other code variations like C#, C++, Java, etc. I will be releasing my full image optimization form project relatively soon; I'm just finishing up a few additional functions before it gets tested.
I updated the ConvertTo-PfW.exe, as it now handles the editing of the internal image's XML using a .NET Framework method type written in C#, though also has its ImageX backup method. ImageX is now parsed into the executable itself and is not a secondary tool. I also changed the executable's GUI output, as now it utilizes the console screen as opposed to outputting just readable content to a GUI form. I did this in order to support passthru and pipable objects; and the console's HostUI has been formatted with better height, width and X/Y axis proportions. I'll be adding the ability for UEFI ISO remastering upon conversion completion by issuing a Yes/No prompt before saving the WIM to the desktop folder.
Hi All, Thanks to @GodHand and a few others I figured I try to get an activated VM with Windows 10 Pro Workstation. The steps I followed; Install windows 10 insider preview 16257 ISO. Skip key. Switch to WS with slmgr /ipk ...-XD863 Rebooted and verified activation. Generate genuineticket.xml with gatherosstate.exe from a Windows 10 1709 x64 ISO. Cloned an existing Windows 10 1709 (16299.125) (changing its UUID thus breaking its activation) Reset activation Stop clip svc (sc stop clipsvc) Go to c:\programdata\windows\microsoft\ClipSVC Delete tokens.dat Install genuineticket.xml from insider build into GenuineTickets folder Reload licenses - slmgr.vbs /rilc Rearm activation - slmgr.vbs /rearm Switch to workstation using the generic key (slmgr.vbs /ipk ..-2YV77) Reboot Once booted, I had an activated Windows 10 for Workstation with a digital license. However, it was an "edition switch". Code: MRP - OEM Query Tool v45.0 Enhanced -- 01/09/2018 {UTC} -- 02:11am ------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Version {WMIC} - Microsoft Windows 10 Pro for Workstations x64 OS Edition {Registry} - ProfessionalWorkstation OS Edition {CBS} - Professional OS Build Number - 16299 OS Update Build Revision - 125 So using @GodHand's Convert-to-PfW, I generated an ISO of Window 10 PFW, and performed a fresh install over the activated edition switch version (made sure to delete the partition so it wan't upgraded -- VM UUID and hence HWID were maintained for the process) After install, I had a fully activated Windows 10 Pro for Workstation Code: MRP - OEM Query Tool v45.0 Enhanced -- 01/09/2018 {UTC} -- 6:39pm ------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Version {WMIC} - Microsoft Windows 10 Pro for Workstations x64 OS Edition {Registry} - ProfessionalWorkstation OS Edition {CBS} - ProfessionalWorkstation OS Build Number - 16299 OS Update Build Revision - 15 {Baseline Release} Right now I'm watching it struggle to install updates.. Code: 2017-12 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4054517) - Error 0x80070002 So.. business as usual? Anyhow, just letting you know this method still works as a way to get digital license for window 10 PfW. Might be worth doing before the next release drops hopefully with the windows update bugs sorted.
We have been doing that manually for months now, and pro-ws is not in the applicability list of the updates, that's why it errors at the updates. And this was on a VM on which i discovered the old product.ini key activated pro-ws and when upgraded it got a HWID, still valid: https://forums.mydigitallife.net/th...l-project-mrp-mk3.71555/page-109#post-1402627
Absolutely, I'm not implying I did anything new, just pointing out what you and others achieved earlier still works as long as you have a copy of 16257 lying around. I'll have to look a little more closely at what the the MRP's role in this is. I note that what you have is still an edition change, is that the correct way to get the ProWS features and still have updates working? (ie, Don't use Convert-to-PfW and build a PfW only install) Are you using MRP to somehow build an installer (wim or iso) that doesn't need the mutliple installs and upgrades to activate a new machine with a digital certificate? Does build 17063 include fixes for PfW that correct the update issues in 16299? Sorry, I have so many questions. I was planning on using a VHD boot with 16257 in my laptop, followed by a 16299 (or 17063) upgrade to get a HWID activated copy of PfW, but if I can skip 16257 it would definitely save time. Thanks.
Excellent. I'l give it a try. Still not sure what role MRP is playing in this. Edit1: I jumped on the insider web site and the options are 17025 and 16299. Where does 17063 come from? My apologies for the ignorant questions , I've not been paying enough attention for windows 10 recently. In the real world I do IOT embedded Linux development.. Windows to me is what a raspberry pi is to most windows users..... a novely I just want to see what the fuss is about... Edit2: Sorry, I think I just realised I'm on the slow ring.. need to get on the fast ring for that build.
The "role" mrp is playing in this, the testing of the MRP on new sku's and builds It shows what is installed and what options were able to run on the new build and how it got activated.
Interesting, 17025 was revoked due to errors in internal CAB signing . 17063 is latest Insider Build. 16299 is Fall Creators Update, the insider tag is a bit misleading.