no. do not think it is mui dvd from its name. it's hyper-v setup iso. i think "mu" means multilanguage because at setup it shows to select different languages to install. i do not know how they are different both isos. i have both of them but have not tested en_zh-tw_hyper-v_server_2008_x64_dvd_x14-87931.iso yet.
Oh, you were right. en_zh-tw only includes English and Trad. Chinese. "mu" DVD is just a multilanguagal ISO not language packs consisting of lp.cab files.
I just managed to port the packages for 9200.16384 from amd64 to x86. This helped me to install 8155 (this build is x86 only) on current date. However I can't activate it. Also I can't change the desktop wallpaper. I just decided to include log files to allow you guys to analyze better. Spoiler: Windows 8 build 8155 Installed on Current Date @maxtorix, @liliactr
I do not understand. Why do you port x86 packages from amd64 build. 9200.16384 has already x86 version. There are version mismatch between builds. As i see you did not change version of packages. There are so many servicing stack and access denied errors. How it helped you to install. Current iso not installable? Change desktop can be done only after activation. Should be related with that. As there is no language packs for my language i am not interested in such betas but at that time windows 8 developer preview was the best operating system microsoft has ever build. It was working flawlessly. They converted it to garbage as windows 8 As i know activation achieved just copying files not with adding them with dism. I had done like that previously and it works.
Can you list me the names of the files with folder structure? I tried to manually copy them, but I ran into activation issues with Windows Vista & 7 Betas. I was not able to login.
Main thread/post updated with [Update from February 21, 2025] - Related to Windows 7 specific procedure
Main thread/post updated with [Update from March 02, 2025] - Related to Windows OS versions from NT5.X era (2000/XP/2003)
Main thread/post updated with [Update from March 10, 2025] - Related to Windows Vista specific procedure
Why do not you use Server 2008 r2 files? and use server 2012 r2? If you change that values also change HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DefaultProductKey/2 values too. For betas better to use betaarchive method. Oobe will continue to work.
I'd not prefer to use that method since I failed to understand that method. Replacing tokens.dat and activation files did not work for me. Also the topic is not detailed enough to understand. It could be exclusive to Windows 8 or 10 betas. I'm focusing on Windows Vista & 7 betas more. As for Server 2008 R2 files, it uses .manifest files not .mum files. I could not extract enough files.
2008 r2 files shared here post #14 https://forums.mydigitallife.net/th...ation-method-all-versions.88772/#post-1861941