Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

greenhillmaniac

Member
  • Content Count

    449
  • Joined

  • Last visited

  • Days Won

    7
  • Donations

    $0.00 

Posts posted by greenhillmaniac

  1. 1 hour ago, win32 said:

    Does anyone know which version is the last one to work and the first one to fail (on RTX 2xxx and GTX 1xxx of course)? I already did a quick mod of 460.89's main kernel mode driver looking at the version checking spots that didn't seem to be in the earlier (372.70 for example) ones I've checked.

    The first driver version to support the RTX 3060 TI was the 457.51 (I keep an archive of all the drivers for this card).

    I tested this version as soon as I acquired the card on 8.0, and it Code 43'd on me right away.

     

    • Upvote 1
  2. There, the Mega link is updated. Enjoy :)

    Since this update repository is now a bit more generic and not necessarily NT 5.x oriented, I'm not sure if the topic should be moved. I'll leave it up to the moderators to decide it.
    Also, I don't know how to put a link in spoiler tags, but I think they would be appropriate for the repo link. If anyone wants to tell me how to do it, I'd appreciate it.

    • Like 1
  3. To everyone: sorry for not updating this thread when I said I would. I'll be going through my external HDD and uploading all of the updates I have onto Mega. This includes the Windows ME updates provided by @RoboSkirt (seriously, much appreciated!) and some (not all) Windows 95 and 98 updates in Portuguese. I manage to scavenge a lot of them through archive.org and a heap of other collections. These include:

    • Internet Explorer 4.01 SP2
    • Internet Explorer 5.5 SP2
    • Internet Explorer 6.0 SP1
    • Windows Media Player 6.4
    • Windows Media Player 7.1
    • Windows Media Player 9

    You get the picture. I've also got Windows POSReady 2009 updates, since that has also gone EOL in the meantime. Windows 2000 also includes a whole lot of Hotfixes not released on regular Windows Update.

    • Like 2
  4. On 10/11/2020 at 10:31 AM, Regele said:

    Do you still have the updates? If so please update the links because these are broken. :D

    Forgot about this thread. I rearranged some items in my Mega account, and those links got expired. I'll update them as soon as I can.

    • Like 1
  5. 1 hour ago, whiteindian said:

    1. Is it necessary to install the KB947821 before your updates ?

    Is that the System Update Readiness Tool? I think you only need that if you have trouble installing updates. If your system was freshly installed, there's no need.

    1 hour ago, whiteindian said:

    2. Does it make a difference to install your updates in random order?  Is that correct > General > Net Framework > Security > Hotfixes > etc. 

    I usually go: Platform Update + Suplement > Internet Explorer 9 > Net Framework 3.5, 4.6 and updates > Powershell 2.0 + BITS 4.0 > Media Player 11 > General > Security > Hotfixes
    The idea is to install as many updated components as possible before moving on to the General, Security, etc updates. That way, the updates will cover a wider range of software.

    1 hour ago, whiteindian said:

    3. Does it make sense to install some Windows Server 2008 updates after your updates post #1: https://mega.nz/folder/txxRyLzC#1vBMGzMHiL864f3bl1Rj1w

    I'd say so, yeah. The main one would be the TLS 1.1 and 1.2 updates, but you can also add the SHA2 updates (they do make Windows Update non functional, but @abbodi1406 managed to make it work regardless. go to MDL and you'll find it)

    1 hour ago, whiteindian said:

    4. Where can I find download links for up-to-date ISO images of Windows Vista

    In here you won't find any. It's usually best if you create your own.

    • Like 3
  6. 2 minutes ago, syria! said:

    Which AMD gpu do you use? I use the Radeon HD 7000 Series GPU and I got it working using SDI

    I have a R9 380, precisely the point where AMD drivers stopped working. Had to used a hacked together Embedded version of the drivers. Not ideal.

    Never heard of SDI. I'll have to check it out.

    EDIT: Yeah, your GPU still had officially compatible drivers with Vista, that's why SDI (Snappy Driver Installer?) found a matching pair.

    • Upvote 1
  7. 1 hour ago, hjaiak12 said:

    Is there a internet archive mirror of this? Or is it exclusive to MEGA?

    So far I have it on Mega and my external HDD. Don't know if I can put in on Archive.org

    1 hour ago, hjaiak12 said:

    Does that include subfolders? (say there's another folder with updates, does it include the ones in the other folder, or is it just the ones exclusively in the general folder?)

    If you want to include subfolders just add the /s switch to forfiles.

  8. 11 hours ago, Vista'erest said:

    Ooh ok thanks for that information about pkgmgr not being able to show any visual progress. But what about a log file? Could that be created as the updates are being installed then? I was messing around with a script I found awhile back that I posted in here that installed all the msu, exe, msp, and cab files. It also leaves a log that can be referenced readily at anytime during the Vista updates installation. BUT, I chose not to use it for these cab files because it makes a mess of the update folder where all the updates are. It scatters the .cat, manifest, mum files and x86 folders everywhere through the location folder, not to mention, that it swells the folders to triple the size. The way you created your cab install *.bat file was great and simple because it contains all the files for deletion later. I just thought if it could create a log too, it would be the icing on the cake. I'm not sure if logs can be created because I'm not a programmer and please excuse me for this request if it cant be done, because I have no idea. But many thanks again for what you have provided so far!! :)

    InstallUpdatesh.Vbs_.vbs 3.23 kB · 0 downloads

    You can use the /l flag to create a log. It would go something like this:

    start /w pkgmgr /ip /m:C:\Update\update.cab /s:C:\Sandbox /l:C:\log.txt

     

  9. 15 hours ago, Vista'erest said:

    but I was wondering if there was any way of creating a cmd prompt or text file to see the installs in real time?

    Unfortunately, as far as I know, pkgmgr does not show any visual progress on update installation, unlike its successor, Dism. When an update is not applicable or has been superseded, pkgmgr simply doesn't install it, so you shouldn't have to worry too much about that. As long as you install updates in the correct order (from oldest to newest, installing first the Platform Update alongside IE9), you should be gold.

    I guess you could just install the Windows 7 AIK and adapt the script to use Dism, as it will act as a wrapper for pkgmgr, but I'm not sure it displays any more information.

  10. On 8/24/2020 at 12:51 PM, XPHomeSP3 said:

    I guess what I should have asked was whether the Server 2008 updates that can be applied to Vista suffer from telemetry being baked in to their Security Monthly Quality Rollups like Windows 7 and 8.1 do.

    It does not. MS never bothered to port DiagTrack to NT 6.0.

    • Like 3
  11. 50 minutes ago, asdf2345 said:

    Wouldn't it be easier to install the updates needed for SHA-2, then update Vista?

    SHA2 updates disable Windows Update, since they bump the build number to 6003

    4 hours ago, TECHGEEK said:

    Do you install the pre-EOL updates through pkgmgr in CMD? I am asking this as my knowledge of this is almost nil.

    Yes, you open command prompt with admin rights, then run the commands. I recommend you put the updates in a path with no spaces, like "C:\Updates", just so it's easier to run the commands.

    • Like 1
  12. 6 hours ago, TECHGEEK said:

    1. Is there any method to install .cab updates from @greenhillmaniac's pre-EOL update repository other than slipstreaming?

    Yes, I mention it in the thread.

    6 hours ago, TECHGEEK said:

    2. Is it pointless to install Server 2008 updates from @greenhillmaniac's other repository without installing pre-EOL updates?

    Not entirely, but it is recommended that you install previous updates first. Some of the newer ones might not install without pre-requisites.

    • Like 1
  13. Yeah, I posted it in a thread somewhere and it got lost to time (I can't find it either!). I still have those drivers archived: https://mega.nz/file/wgxAFCzJ#N8_D1L59p8isZ2Gz4nmgBPxkdXlFqS52uxbctbvumDQ

    They're AMD Embedded drivers based on an early 15.100 branch, still compatible with Vista. To use your R9 300 GPU (or any other, since it has few cards listed) with them you need to edit the INF and add your HWID (I think I added my GPU's HWID in that archive, the R9 380, so you could use that as the baseline for changes specific to your card).

  14. I have a pertinent question... Why create a thread, when this topic is already being discussed:

    Furthermore, you're linking to the Server 2008 update repository that I created without any kind of credit.
    Honestly, this thread seems pointless... :crazy:

    • Upvote 4
  15. 15 minutes ago, xpclient said:

    Great so I got all English files installed now. With this batch file, I installed all the cab ones without making any mess of tons of files in the folder where the cabs themselves are located:

    md %tmp%\Updates
    cmd /c for %%U in (*.cab) DO pkgmgr /ip /m:"%%U" /s:"%tmp%\Updates" /quiet /norestart
    rd %tmp%\Updates /q /s

    The main advantage of creating a folder for each update is that all the extracted files that pkgmgr extracts will be contained in them. It's easier to maintain and then delete. Plus, I had a few errors (not sure why) when trying to install without specifying a temporary directory, so I like to do it just in case.

  16. 17 hours ago, xpclient said:

    @greenhillmaniac, which updates exactly are language-specific? I noticed some Ultimate Extras folders were named in Portuguese. I did find the updates with pt-pt or ptg in their file names. Any others too? Are Ultimate Extras non-English?

    The updates that say pt-pt or ptg are in Portuguese. All others are language neutral. In fact, the Ultimate Extras are language neutral (forgot to change the folder names). I'd estimate only an extremely small amount of them are specific to my language.

    On 8/8/2020 at 11:26 PM, docR said:

    It's Ultimate, but the Ultimate Extras aren't pre-installed. (i'll look into releasing the image later) Is there any way to package those into offline msu's too? Bit concerned about that since they could disappear from Microsoft servers without warning.

    Just install the "cab" files through pkgmgr. Works just like you installed them through Windows Update. If you give that Ultimate Extras folder to your friend, he should know how to integrate them into the ISO.

    On 8/8/2020 at 8:23 PM, IntMD said:

    By the way, have you crosschecked with what daniel_k's got to see if there are update urls that you didn't get but he did? Just to make sure we get this s*** complete.

    I did go multiple times through this list at the time I compiled it, but I'll try to see what daniel_k has.

    • Like 1
  17. Big thanks to @daniel_k for discovering this method.

    Tools you'll need:

    This tutorial applies to both AMD64 and X86.

    1. Download all 3 parts of Standard_8_64Bit_Bootable_IBW if using 64 bit, or all 2 parts if using 32 bits, and open part 1 to extract the ISO. After this you should have Standard_8_64Bit_Bootable_IBW.iso or Standard_8_32Bit_Bootable_IBW.iso
    2. Open the ISO with 7-Zip and navigate to "sources/install.wim". Right click on the install.wim and select "Open inside".
    3. Inside the install.wim, go to "Windows/servicing/Packages"
      Here's where it differs for both architectures.
      For 64 bit copy the following files into a folder in your computer:
      Quote

       

      
      Microsoft-Windows-Embedded-SKU-Foundation-Package-admin~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-admin~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-base~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-base~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-com~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-com~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-drivers~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-drivers~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-ds~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-ds~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-enduser~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-enduser~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-inetcore~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-inetcore~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-mergedcomponents~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-mergedcomponents~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-mincore~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-mincore~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-minio~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-minio~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-minkernel~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-minkernel~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-net~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-net~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-printscan~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-printscan~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-sdktools~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-sdktools~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-shell~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-shell~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-termsrv~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-termsrv~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-windows~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-windows~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.mum

       

      For 32 bit copy the following files:

      Quote

       

      
      Microsoft-Windows-Embedded-SKU-Foundation-Package-admin~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-admin~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-base~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-base~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-com~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-com~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-drivers~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-drivers~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-ds~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-ds~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-enduser~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-enduser~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-inetcore~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-inetcore~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-mergedcomponents~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-mergedcomponents~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-mincore~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-mincore~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-minio~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-minio~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-minkernel~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-minkernel~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-net~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-net~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-printscan~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-printscan~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-sdktools~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-sdktools~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-shell~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-shell~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-termsrv~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-termsrv~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package-windows~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package-windows~31bf3856ad364e35~x86~~6.2.9200.16384.mum
      Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~x86~~6.2.9200.16384.cat
      Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~x86~~6.2.9200.16384.mum

       

       

    4. Next go to "Windows/winsxs/Manifests" and...
      For 64 bit copy these files into the same folder you extracted the previous ones:
      Quote

       

      
      amd64_microsoft-windows-e..-drivers-deployment_31bf3856ad364e35_6.2.9200.16384_none_4444b38b4ac9d2cc.manifest
      amd64_microsoft-windows-e..-enduser-deployment_31bf3856ad364e35_6.2.9200.16384_none_4e0ff941ac83cf57.manifest
      amd64_microsoft-windows-e..-mincore-deployment_31bf3856ad364e35_6.2.9200.16384_none_b1615a47d2a0b72a.manifest
      amd64_microsoft-windows-e..-termsrv-deployment_31bf3856ad364e35_6.2.9200.16384_none_131cc4307865811c.manifest
      amd64_microsoft-windows-e..-windows-deployment_31bf3856ad364e35_6.2.9200.16384_none_be960147c47f915c.manifest
      amd64_microsoft-windows-e..age-base-deployment_31bf3856ad364e35_6.2.9200.16384_none_8784fd06875ea0f8.manifest
      amd64_microsoft-windows-e..ckage-ds-deployment_31bf3856ad364e35_6.2.9200.16384_none_c995e55f1dc9533e.manifest
      amd64_microsoft-windows-e..ge-admin-deployment_31bf3856ad364e35_6.2.9200.16384_none_93f5fafac0c8e9d2.manifest
      amd64_microsoft-windows-e..ge-minio-deployment_31bf3856ad364e35_6.2.9200.16384_none_e0bddbe35cd9a2e9.manifest
      amd64_microsoft-windows-e..ge-shell-deployment_31bf3856ad364e35_6.2.9200.16384_none_4138dcc43b8b0da7.manifest
      amd64_microsoft-windows-e..inetcore-deployment_31bf3856ad364e35_6.2.9200.16384_none_25eb92fb03493a30.manifest
      amd64_microsoft-windows-e..inkernel-deployment_31bf3856ad364e35_6.2.9200.16384_none_b333814628fd821a.manifest
      amd64_microsoft-windows-e..kage-com-deployment_31bf3856ad364e35_6.2.9200.16384_none_774cef83dac211a4.manifest
      amd64_microsoft-windows-e..kage-net-deployment_31bf3856ad364e35_6.2.9200.16384_none_96316194079798a2.manifest
      amd64_microsoft-windows-e..mponents-deployment_31bf3856ad364e35_6.2.9200.16384_none_51d8b393b2f07e97.manifest
      amd64_microsoft-windows-e..rintscan-deployment_31bf3856ad364e35_6.2.9200.16384_none_1b35530e67f98a3d.manifest
      amd64_microsoft-windows-e..sdktools-deployment_31bf3856ad364e35_6.2.9200.16384_none_6f9fd3dc23f6d73a.manifest

       

      For 32 bit copy these files:

      Quote

       

      
      x86_microsoft-windows-e..-drivers-deployment_31bf3856ad364e35_6.2.9200.16384_none_e8261807926c6196.manifest
      x86_microsoft-windows-e..-enduser-deployment_31bf3856ad364e35_6.2.9200.16384_none_f1f15dbdf4265e21.manifest
      x86_microsoft-windows-e..-mincore-deployment_31bf3856ad364e35_6.2.9200.16384_none_5542bec41a4345f4.manifest
      x86_microsoft-windows-e..-termsrv-deployment_31bf3856ad364e35_6.2.9200.16384_none_b6fe28acc0080fe6.manifest
      x86_microsoft-windows-e..-windows-deployment_31bf3856ad364e35_6.2.9200.16384_none_627765c40c222026.manifest
      x86_microsoft-windows-e..age-base-deployment_31bf3856ad364e35_6.2.9200.16384_none_2b666182cf012fc2.manifest
      x86_microsoft-windows-e..ckage-ds-deployment_31bf3856ad364e35_6.2.9200.16384_none_6d7749db656be208.manifest
      x86_microsoft-windows-e..ge-admin-deployment_31bf3856ad364e35_6.2.9200.16384_none_37d75f77086b789c.manifest
      x86_microsoft-windows-e..ge-minio-deployment_31bf3856ad364e35_6.2.9200.16384_none_849f405fa47c31b3.manifest
      x86_microsoft-windows-e..ge-shell-deployment_31bf3856ad364e35_6.2.9200.16384_none_e51a4140832d9c71.manifest
      x86_microsoft-windows-e..inetcore-deployment_31bf3856ad364e35_6.2.9200.16384_none_c9ccf7774aebc8fa.manifest
      x86_microsoft-windows-e..inkernel-deployment_31bf3856ad364e35_6.2.9200.16384_none_5714e5c270a010e4.manifest
      x86_microsoft-windows-e..kage-com-deployment_31bf3856ad364e35_6.2.9200.16384_none_1b2e54002264a06e.manifest
      x86_microsoft-windows-e..kage-net-deployment_31bf3856ad364e35_6.2.9200.16384_none_3a12c6104f3a276c.manifest
      x86_microsoft-windows-e..mponents-deployment_31bf3856ad364e35_6.2.9200.16384_none_f5ba180ffa930d61.manifest
      x86_microsoft-windows-e..rintscan-deployment_31bf3856ad364e35_6.2.9200.16384_none_bf16b78aaf9c1907.manifest
      x86_microsoft-windows-e..sdktools-deployment_31bf3856ad364e35_6.2.9200.16384_none_138138586b996604.manifest

       

       

    5. Now here's the interesting part. Open command prompt with Admin privileges and run:
      If using 64 bit:
      dism /online /add-package /packagepath:<path to folder>\Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.mum

      If using 32 bit:

      dism /online /add-package /packagepath:<path to folder>\Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~x86~~6.2.9200.16384.mum
    6. Reboot and install IE11 like you normally would. This time it will finish the installation and prompt you to reboot. After that, IE11 will be fully operational on your machine!

    Here's some pics of the results:

    Quote

    9yfRn7A.png

    KtKtYBf.png

     

    • Upvote 4
×
×
  • Create New...