It seems to be in winsxs Windows\WinSxS\amd64_microsoft-windows-editions-professional_31bf3856ad364e35_6.3.9600.16384_none_cd3b0950ee5b54c1 View attachment UpgradeMatrix.zip
Manually adding UpgradeMatrix.xml to Code: C:\$WINDOWS.~BT\Sources\Panther\UpgradeMatrix\Professional does not work.
Does anyone know which file in Sources that calls this command below? If so that would be a solid lead as to why Windows 8.1 doesn't use the UpgradeMatrix.xml files. The code below is from the Windows 8 setup log. Code: 2012-12-28 20:55:04, Info CMediaSetupInstallMatrix::Initialize: Trying to retrieve Install Matrix file from Install.WIM 2012-12-28 20:55:04, Info Install.WIM = G:\Sources\install.wim 2012-12-28 20:55:04, Info Image Index = 1 2012-12-28 20:55:04, Info Working Dir = C:\$WINDOWS.~BT\Sources\Panther 2012-12-28 20:55:04, Info Edition Id = Professional 2012-12-28 20:55:04, Info CMediaSetupInstallMatrix::Initialize: Successfully extracted Install Matrix file: [C:\$WINDOWS.~BT\Sources\Panther\upgradematrix\Professional\UpgradeMatrix.xml]
You're making it way harder than you need to. Mount install.wim index:1 copy the mount\windows\servicing\Editions\upgradematrix.xml to your desktop or wherever. Edit the file so that you can do full upgrades and keep nothing on all versions by doing an alt-h to replace fullUpgrade="false" with fullUpgrade="true" Save file and copy it over the file in the mount folder again I believe this will enable the "Keep nothing" option for online setup for any version that was previously set to false. I'm not exactly sure that there is anything more you can do with upgradematrix.xml I'm not even sure it's a good idea. Some older OS versions might have a bunch of registry settings and programs that you don't want to import into Win81. This is why I don't mess with the default settings of a lot of these xml files.
See the PM I sent you. I am not making it harder than I need to. M$ disabled use of the UpgradeMatrix.xml file using .\Sources\Setup.exe causing an Error when using an AIO disc and EI.cfg. I am not trying to modify the UpgradeMatrix.xml to install on unsupported versions, I'm trying to get upgrading to work! Keep in mind all my testing is using a Windows 8 Pro x64 install and none of the upgrades work from an AIO disc. If I use a x64 4-in-1 with no EI.cfg and insert the keys it works. The point of what I am trying to do is an 8-in-1 with x86 and x64 upgrades working just like I did in Windows 8 without needing the key during setup.
I think they did that on purpose so that it won't load upgradematrix.xml unless you enter a valid key. Perhaps copying the upgradematrix.xml stuff to the boot.wim could accomplish your goal.
When doing upgrades the UpgradeMatrix.xml is never touched on the boot.wim. It is pulled from the Install.WIM and moved to the .\$WINDOWS.~BT\Sources\Panther\upgradematrix directory. See a few posts up on what I found.
It could be that setup is just giving a misleading error message. When it says that the upgrade path is not supported, it could be a generic errorlevel error message. What I mean is that it could be causing a problem back from when no key was entered.. What we could do is a /dism /set-productkey set to the default key for an index and see if it still gives that upgrade path garbage error. I'll test it out, but it's going to be a bit as I have to re-install vmware since I upgraded and need to install a baseline OS to upgrade FROM.
I still have the CN Leak. Let me look at that file. Also, let me do some testing with the Enterprise discs. You bring up a very valid point with those. EDIT: Don't think it makes one bit of a difference for that MediaMeta.xml file being gone. Code: <?xml version="1.0"?> <mc> <media> <chunk>enterprise_zh-cn_vl</chunk> <taskguid>54a60d89-2228-42ff-a11c-0dd469de63fe</taskguid> </media> </mc>
hmm yer probably right. I'm just starting on the first install to see if setting the product key helps now... Just to verify, that .tmp file contents was the stuff with "info:" right? that wasn't the upgradematrix in disguise? google searching seems to indicate that mediameta.xml is some sort of dvd authoring type of file. I don't think it has any bearing on our situation
Just tried using the RTM copy of Enterprise x64 which has the EI.cfg specified and when running from .\Setup.exe it works fine however and extracts the UpgradeMatrix.xml and allows upgrade but the second you run it from .\Sources\Setup.exe it's the same error "This upgrade path is not supported. Please close Setup and re-launch from the root of the media or go back and pick a different installation choice." This would work fine but for an x86/x64 AIO you have to change the Sources directory and where the Install.WIM is so it loads it in the old looking Windows 7 installer. EDIT: I wonder if using the Windows 7 setup files will work better considering that the Windows 8 setup files broke the install during upgrade.
See that might be hinting that it's passing some info between the root\setup.exe and the root\sources\setup.exe I'm thinking that the product key might be some sort of solution here, but I'm still testing... It'll be a little bit before I even get this original x86 win8.0 to install to test upgrade... I'll update here on my results on the dism /set-productkey in a bit