Is It Possible To Build Your Own Windows 8.1 Pro+WMC ISO?


Recommended Posts

Now that windows 8.1 has leaked, many people who had installed win8+WMC wanted to install win8.1 Pro+WMC, and have it activated. There are numerous posts on the web telling people how to do it, but it is clumsy and sometimes fail.

 

Actually you can build your own win8.1Pro+WMC installation ISO, using DISM in build 9600, but I guess the procedure might be considered warez in Neowin, so I better not elaborate, instead show some screen-shots: yes, it can be done. :)

 

screen1515.jpg

 

screen1516.jpg

 

When the ISO is done, it is specific to your WMC key, and you can use it to install or re-install, notice that Net.3.5 was also added to install.wim :

 

screen1517.jpg

 

The WMC key is bundled to the machine it was first installed and activated, so, if win8.1Pro+WMC is installed on the same machine on-line, it will activate by itself, otherwise you will need to find out the possibilities of activating it if installed on another machine(like in my case, installed on VM).

 

 

Where and how do you get the "Internal" name and source path for the features?

You mean .Net 3.5?

 

http://msdn.microsoft.com/en-us/library/hh506443.aspx

 

Actually, if you make everything from your legit win8, win8.1, legit key, then it's not warez, that's why MS has DISM for people to work on, and the commands to apply.... but I'd rather be on the safe side and avoid the ban-hammer. :)

You mean .Net 3.5?

 

http://msdn.microsoft.com/en-us/library/hh506443.aspx

 

Actually, if you make everything from your legit win8, win8.1, legit key, then it's not warez, that's why MS has DISM for people to work on, and the commands to apply.... but I'd rather be on the safe side and avoid the ban-hammer. :)

Thanks. I do have 3 legitimate copies of Windows 8 so I might try this.

 

What I was wondering after seeing the command

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs

 

Is there a way to get the list of names for all the other features as well source path for each of them since D:\Sources\SXS may not contain the installers for each of those features.

havent installed win8.1 yet. how to use 9600 dism in 9200?

LOL, out of my depths, hope some geek could answer you.

 

Thanks. I do have 3 legitimate copies of Windows 8 so I might try this.

 

What I was wondering after seeing the command

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs

 

Is there a way to get the list of names for all the other features as well source path for each of them since D:\Sources\SXS may not contain the installers for each of those features.

Hope this helps : http://technet.microsoft.com/en-us/library/hh824822.aspx

I'd imagine so. Prepare your image as per usual, use something to capture it to a WIM, dump the source files to disk (and replace install.wim with your captured wim) and then use an app like wintoolkit to make a bootable ISO

If someone were to go through all this trouble, would they be able to upgrade their Windows 8 Pro with WMC to 8.1 Pro with Media Center with this ISO, or can it only be used for a clean install/a "Keep nothing" upgrade?

If someone were to go through all this trouble, would they be able to upgrade their Windows 8 Pro with WMC to 8.1 Pro with Media Center with this ISO, or can it only be used for a clean install/a "Keep nothing" upgrade?

AFAIK, it's only good for clean installs. :)

OT, can I do a clean install from retail 8.1 disc with my old w8 key?

Sure you can do that, but you need to enter the generic key on installation because it won't accept win8 keys, after installation enter your win8 key and activate - or - add a EI.cfg file to the ISO sources folder, then it won't ask for key on installation (I think it involves more work, unless you think of frequent re-installs).

You can also allow it to accept an upgrade key during OOBE if you place an ei.cfg in the /sources folder with the following information:

 

Channel

_Default

Sure you can do that, but you need to enter the generic key on installation because it won't accept win8 keys, after installation enter your win8 key and activate - or - add a EI.cfg file to the ISO sources folder, then it won't ask for key on installation (I think it involves more work, unless you think of frequent re-installs).

 

Why did they do that? Why not allow us to do a clean install?

To-day's Neowin News has quoted a blog from ZDNet

 

https://www.neowin.net/news/some-microsoft-volume-licensees-will-have-to-wait-to-get-windows-81

 

But it seems MJF had not read deep enough in the MSDN blog, 

 

http://blogs.msdn.com/b/stevengu/archive/2013/09/09/download-windows-8-1-rtm-visual-studio-2013-rc-and-windows-server-2012-r2-rtm-today.aspx?PageIndex=4#comments

 

Because Steve Guggenheimer had made a reply in the comments section which I guess many people would be interested to know:

 

  1. screen_134_zpsc22977f6.jpg

:laugh:

Sure you can do that, but you need to enter the generic key on installation because it won't accept win8 keys, after installation enter your win8 key and activate - or - add a EI.cfg file to the ISO sources folder, then it won't ask for key on installation (I think it involves more work, unless you think of frequent re-installs).

Has MS posted what the generic keys are for this yet?

This topic is now closed to further replies.
  • Posts

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      149
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!