Hi moderate Thank you share windows appx. I discover the "Microsoft.NET.Native.Runtime.1.0_1.0.22929.0_x64__8wekyb3d8bbwe.appx" and "Microsoft.NET.Native.Runtime.1.0_1.0.22929.0_x86__8wekyb3d8bbwe.appx" The two appx version is 1.1 not 1.0. I check the AppxManifest.xml content. The Identity Name is Microsoft.NET.Native.Runtime.1.1 and Version is "1.1.23109.0" Can you check it and do you have real 1.0 version Microsoft.NET.Native.Runtime? Thank you Code: <?xml version="1.0" encoding="utf-8"?><Package xmlns=" schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:uap=" schemas.microsoft.com/appx/manifest/uap/windows10" xmlns:mp=" schemas.microsoft.com/appx/2014/phone/manifest" IgnorableNamespaces="uap"> <Identity Name="Microsoft.NET.Native.Runtime.1.1" ProcessorArchitecture="x64" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" Version="1.1.23109.0" /> <mp:PhoneIdentity PhoneProductId="a4aa3085-0269-462d-a216-ee1bfb292b29" PhonePublisherId="a8099e80-050d-411d-9b45-4ea107a7be6b" /> <Properties> <Framework>true</Framework> <DisplayName>Microsoft .Net Native Runtime Package 1.1.23109.0</DisplayName> <PublisherDisplayName>Microsoft Corporation</PublisherDisplayName> <Description>Microsoft .Net Native Runtime Package 1.1.23109.0</Description> <Logo>logo.png</Logo> </Properties> <Resources> <Resource Language="en-US" /> </Resources> <Dependencies> <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.10049.0" MaxVersionTested="10.0.10049.0" /> </Dependencies> </Package>
It is all MS fault. Because MS did silent update in VS2015. But be happy. You have 1.1 version instead 1.0.
Hi moderate I need 1.0 version because I need to customize wim install source in windows 10. I went to keep only windows store app in wim. But if I remove xbox app. The windows store app will does not install success. So I check windows store app mini requirement that need Microsoft.NET.Native.Runtime.1.0. If I use 1.1 version will not match the mini requirement. Or have other method that can keep windows store app normally run. And remove xbox app success?
BTW: Offtopic Does anybody (abbodi) have a repo for W8-0-0 APPXes? I can't download: Skype (both x64 and x32 for W8-0-0) Photos (both x64 and x32 for W8-0-0) It looks like MS has removed them or something.
You expect someone to download 3,39GB just to get one or more files? how about you make a mega.nz folder with individual files W8-0-0 is deprecated
Hi moderate Unfortunately the two appx unable work. Install show error message "The Appx package's block map is invalid." msdn.microsoft.com/zh-tw/library/windows/desktop/hh446767(v=vs.85).aspx#use_app_packager I research the document. Can use app packager to create appx file. Does this method create bulit-in appx success?
Code: C:\Program Files (x86)\Windows Kits\10\bin\x64>MakeAppx pack /d c:\Decomp\x64 /p c:\Decomp\x64.appx Microsoft (R) MakeAppx Tool version 10.0.10011.16384 Copyright (C) 2013 Microsoft. All rights reserved. The path (/p) parameter is: "c:\Decomp\x64.appx" The content directory (/d) parameter is: "c:\Decomp\x64" Enumerating files from directory "c:\Decomp\x64" MakeAppx : warning: Ignoring footprint file "AppxBlockMap.xml". MakeAppx : warning: Ignoring footprint file "AppxMetadata\CodeIntegrity.cat". MakeAppx : warning: Ignoring footprint file "AppxSignature.p7x". MakeAppx : warning: Ignoring footprint file "[Content_Types].xml". Packing 5 file(s) in "c:\Decomp\x64" (content directory) to "c:\Decomp\x64.appx" (output file name). Using "c:\Decomp\x64\AppxManifest.xml" as the manifest for the package. Adding "c:\Decomp\x64\logo.png" to the package as a payload file. Its path in the package is "logo.png". Adding "c:\Decomp\x64\mrt100.dll" to the package as a payload file. Its path in the package is "mrt100.dll". Adding "c:\Decomp\x64\mrt100_app.dll" to the package as a payload file. Its path in the package is "mrt100_app.dll". Adding "c:\Decomp\x64\clrcompression.dll" to the package as a payload file. Its path in the package is "clrcompression.dll". Package creation succeeded. C:\Program Files (x86)\Windows Kits\10\bin\x64>MakeAppx pack /d c:\Decomp\x86 /p c:\Decomp\x86.appx Microsoft (R) MakeAppx Tool version 10.0.10011.16384 Copyright (C) 2013 Microsoft. All rights reserved. The path (/p) parameter is: "c:\Decomp\x86.appx" The content directory (/d) parameter is: "c:\Decomp\x86" Enumerating files from directory "c:\Decomp\x86" MakeAppx : warning: Ignoring footprint file "AppxBlockMap.xml". MakeAppx : warning: Ignoring footprint file "AppxMetadata\CodeIntegrity.cat". MakeAppx : warning: Ignoring footprint file "AppxSignature.p7x". MakeAppx : warning: Ignoring footprint file "[Content_Types].xml". Packing 5 file(s) in "c:\Decomp\x86" (content directory) to "c:\Decomp\x86.appx" (output file name). Using "c:\Decomp\x86\AppxManifest.xml" as the manifest for the package. Adding "c:\Decomp\x86\logo.png" to the package as a payload file. Its path in the package is "logo.png". Adding "c:\Decomp\x86\mrt100.dll" to the package as a payload file. Its path in the package is "mrt100.dll". Adding "c:\Decomp\x86\mrt100_app.dll" to the package as a payload file. Its path in the package is "mrt100_app.dll". Adding "c:\Decomp\x86\clrcompression.dll" to the package as a payload file. Its path in the package is "clrcompression.dll". Package creation succeeded. C:\Program Files (x86)\Windows Kits\10\bin\x64>
I will not work either since MS's MakeAPPX skips: AppxSignature.p7x, AppxMetadata\CodeIntegrity.cat and then requires to add them by SignTool (what can't be obviously done, if you aren't MS), but there there is better option: The 1.1 packages are from VS2015 RTM, so 1.0 packages will be in some VS2015Preview.ISO... I just downloading CTP5 to look at it.
i have one dumb question and sorry also for it : is cumulative update is a bunch of all of update in one archive so i dont have to download the others just the cumulative not the others ? and thanks in advance for your help.
Cumulative is a separate individual update, it doesn't have multiple updates it's cumulative because it contains all fixed code/components that found in previous updates, along with new fixed components thus, cumulative update replaces the previous cumulative update and so on...