Discussion in 'Windows 10' started by Enthousiast, Mar 27, 2018.
I am not sure, i found it online version 4. Do you have the link?
We are at v15, v14 also will work. All info is at the OP.
maybe i didn't sleep haha I checked 10 times and couldn'T findit so I googled. Thanks for pointing this out, I will try ASAP.
I see this thread still live.
You need to login to view this posts content.
17134 is already worse, so it will probably take another build, and the more it takes, the more people will speculate.
Mean time this one works and there is no danger of forced updates so it's a win - win
Running 17133.73 have no problems what so ever.
The mct hack is exactly that batch script - getting official MediaCreationTool to generate 17133 build (RS4) instead of current RS3.
You can't use it for 17134 (but there is not much difference atm between the two, at least none that would concern you).
Adjusted script to work under Windows 7 host OS too (that comes default only with powershell v2) - so redownload / recreate / re-quote so it's up-to-date for others too.
This method does not require any adk!
Not any script needed, just the /selfhost suffix is working to get the mct to use the product.cab to fetch other buids than the mct is made for. @mxman2k's simple front end GUI also does the trick, iirc.
Yeah, was mentioned in the previous post the script is an automation of the "mct hack" method. Ofc you can do it manually. It's very clear what the script does - you click it, it downloads products.xml, downloads mct.exe, edits products.xml with the catalog tags, and launches mct /selfhost. You surely see the convenience value? (at least for the guy having issues with the esd scripts, adk's and etc.)
The convenience value will be when the official rs4 MCT is released and the abbodi1406/mxman2k gui for it to fetch the VL editions too, imho.
The script works, it's very much on-topic, and it's directed as a solution to another member having issues with the proven methods (probably not being well versed into these things).
How is that triggering you like I've rustled your jimmies or something? There is no problem for me to go out of your way for another 9 years or so.
I don't get what you're rambling about, what 9 years of you going out of my way are you talking about? I've been active here for just 5 afaik, before i took the effort to first read all threads, never seen you been active for all of the years i am here.
The only issue i got in 17133.1 was that malware boot time loading driver mabamswissarmy.sys gave BSod , i shifted to new version of it and all is ok.
17133.1 seems quiet good other than this issue , which sees to be application compability issue not a windows kernel issue.