Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


greenhillmaniac

Member
  • Content Count

    388
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by greenhillmaniac

  1. Happy Easter, everybody! I am the Easter bunny bringing my Easter eggs: Replaced Monthly Rollup with the new KB4493471 (located on the root directory of the repository) Added a new Servicing Stack update KB4493730 (located on the root directory of the repository) Added Security Only Updates, KB4489876 and KB4493458 (located in the folder "/Security Only (Post August 2018)") Replaced Internet Explorer Cumulative Update with KB4493435 (located in the folder "/Security Only (Post August 2018)") Added .NET Updates: -KB4488661 for .NET 2.0 SP2 (located in "/NET 2.0 SP2") -KB4488669 for .NET 4.5.2 (located in "/NET 4.5.2") -KB4488666 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1") Added Extra updates KB4490128 (located in "/Extras") with an updated readme file A few notes, as usual: the build number bump is certainly an interesting phenomenon, but sadly an uneventful one (it should've been a new Service Pack). The new Servicing Stack update was released to support SHA2 signing of updates, but no accompanying update (just as a reminder, Windows 7 had both the SS and an additional update). The .NET updates are not Rollups or Security Only, but simply standalones to add support for the new Japanese Calendar, so there's no real need to apply them if you live outside The Land Of The Rising Sun . Lastly, for some reason the new timezone update KB4490128 does not supersede the old timezone updates in the Catalog, so I added it to the Extras folder instead of replacing the older ones with it. https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w
  2. They are porting Chromium to ARM64 so it'll work with Windows 10 on ARM. Recompiling that to ARM32 would require some knowledge of the instruction set, I'd speculate: https://www.neowin.net/news/microsoft-and-google-are-working-together-to-bring-chrome-to-windows-on-arm Firefox also works on ARM64 with the latest dev versions: https://www.windowscentral.com/mozilla-releases-first-nightly-build-firefox-windows-10-arm
  3. My apologies. When I needed to download a hotfix I usually used that link and it redirected to the EULA page. Seems like Microsoft closed that loophole...
  4. Actually, it hasn't been shutdown. Just buried. Use this URL: https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=2990184&kbln=en-us&forceorigin=esmc Accept the EULA and it will redirect you to the KB4343220 page. No worries. Just click the URL again and you'll be in the hotfix download page. Then change the URL to the update KB you want to download Are there any others? I intend on making a compilation of POSReady patches in PT-PT language.
  5. Should also work for newer Ryzen's, seeing you can use the same chipset (in my case B350) with the same functioning drivers. The only thing that's incompatible are the GPU drivers for the Ryzen APUs, since the last AMD GPU drivers compatible with Vista were released in mid-2015.
  6. You can already use the Windows 10 version they're offering to install on any (supported) Windows version you want. Just find a way to download the installer.
  7. Looks can be deceiving, my friend. Just because the embedded PkgProperties on the MSU file says that doesn't mean the update.mum inside the CAB file does Just to prove my point I went ahead and installed Windows 8.0 Enterprise on VMWare to test installing the latest .NET Framework 4.8 preview update (build 3745). If you try to install it normally from the executable, it will fail with an unsupported OS message, as you'd expect: So I basically extracted the CAB files relating to 8.0 from the executable and installed them through Dism: And it seemed to go over just fine. Maybe you'd like to try it and see if you get the same results. I haven't tested this extensively, mind you.
  8. If they do release an ARM version of Edge, it will probably be ARM64 because of the whole Windows 10 on ARM effort they've recently been pushing. AFAIK Windows 8.x RT was made for ARM32.
  9. OK, so from what I've gathered, you managed to mod the nVidia RTX drivers to work on Vista? Have you tested them? Do you have screenshots proving the mod works? Just posting a bunch of files in the wrong section of the forum (this could've been posted in the Windows Vista category) without any kind of description doesn't help people understand why this was posted.
  10. And here is the repository update for Windows 8.0 for January and February 2019: Replaced Monthly Rollup with the new KB4487025 (located on the root directory of the repository) Replaced Flash Player Security update with KB4487038 (located on the root directory of the repository) Added Security Only Updates, KB4480972 and KB4486993 (located in the folder "/Security Only (Post September 2016)") Replaced Internet Explorer Cumulative Update with KB4486474 (located in the folder "/Security Only (Post September 2016)") Replaced .NET Framework Security and Quality with: -KB4483456 for .NET 3.5 SP1 (located in "/.NET Framework 3.5 Updates/Security and Quality Rollup") -KB4483454 for .NET 4.5.2 (located in "/.NET Framework 4.5.2 Updates/Security and Quality Rollup") -KB4483449 for .NET 4.6.x-4.7.x (located in "/.NET Framework 4.6.x-4.7.x Updates/Security and Quality Rollup") Added .NET Framework September Security Only Updates: -KB4480083 and KB4483481 for .NET 3.5 SP1 (located in "/.NET Framework 3.5 Updates/Security Only Updates") -KB4480075 and KB4483473 for .NET 4.5.2 (located in "/.NET Framework 4.5.2 Updates/Security Only Updates") -KB4480070 and KB4483468 for .NET 4.6.x-4.7.x (located in "/.NET Framework 4.6.x-4.7.x Updates/Security Only Updates") Added extra update KB4490516 (located in "/Extras (Non Security Updates)") Can't wait to see how IE11 will work on Windows 8.0... https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ
  11. Ok, I've had time to update the repository with the January and February updates. Just in time, before Microsoft unleash the March ones. Replaced Monthly Rollup with the new KB4487023 (located on the root directory of the repository) Added Security Only Updates, KB4480957 and KB4487019 (located in the folder "/Security Only (Post August 2018)") Replaced Internet Explorer Cumulative Update with KB4486474 (located in the folder "/Security Only (Post August 2018)") Replaced .NET Framework Security and Quality with: -KB4483457 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security and Quality Rollup") -KB4483455 for .NET 4.5.2 (located in "/NET 4.5.2/Security and Quality Rollup") -KB4483451 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security and Quality Rollup") Added .NET Security Only Updates with: -KB4480084 and KB4483482 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security Only") -KB4480076 and KB4483474 for .NET 4.5.2 (located in "/NET 4.5.2/Security Only") -KB4480072 and KB4483470 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security Only") Added Extra updates KB4486459, KB4487354 and KB4490514 (located in "/Extras") with an updated readme file Funny enough, the timezone update KB4486459 does not replace the previous KB4468323. Also worth noting that KB4487354 in the extras folder is not needed if you install the Monthly Rollups. That is all for now https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w EDIT: I've rearranged the repository for easier navigation. Now the pre-Monthly Rollup Security Updates are in a folder named "Security Updates (May 2017-August 2018)"
  12. Wow, I made that post quite a while ago... Yes, I've already figured it out regarding POSReady 7. Both Windows Thin PC and POSReady 7 are derived from Embedded Standard 7, meaning all of the OS is componetized. Updates made only for those specific variants of NT 6.1 don't work on regular W7 but, luckily for us, MS tries to make its job easier and Monthly Rollups are universal for all NT 6.1 variants. Considering they will be selling Extended Support until 2023, I doubt they will start making a distinction between those 2 product lines.
  13. Do you have a plan, budget, milestones and deadlines for such a project? I'm sorry, but you just register into a forum and the first thing you do is ask for people to make a program for you? What did you expect?
  14. So, this solution would be limited to what is archived in archive.org. That is kind of a limitation for everyone except EN-US systems. I recently tried and compile Windows 95 updates in PT-PT, and most (if not all) of the links I found were dead or not archived.
  15. Wow, this is excellent news for Windows 8.0 users! The last Internet Explorer upgrade Microsoft will ever release for a Windows platform. Feels like a historic moment.
  16. Maybe this link will be helpful: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions#partition-layout
  17. Even though updates directed at Windows Embedded 7 are structurally different, because they have to target individual packages since the OS is entirely modular, unlike standard Windows 7, they will be providing extended support to Professional and Enterprise users. Although we probably won't have access to those updates, I very much doubt that MS will go to the trouble of doing different kinds of updates for POSReady 7 and the paying volume license costumers who are using the Extended Support. My guess is that POSReady 7 updates will be identical to those supplied to Professional and Enterprise users after EOL, like it has been so far.
  18. I don't get why people are saying Windows 7 is EOL on 2020... We have at least until the end of 2021
  19. Windows 8.0 sure doesn't get any love... To remedy this, I've got a big repository update for ya! Brace yourselves, it's gonna be a big post. Here's the usual: Replaced Monthly Rollup with the new KB4471330 (located on the root directory of the repository) Replaced Flash Player Security update with KB4471331 (located on the root directory of the repository) Added Security Only Update, KB4471326 (located in the folder "/Security Only (Post September 2016)") Replaced Internet Explorer Cumulative Update KB4483187 (located in the folder "/Security Only (Post September 2016)") Replaced .NET Framework Security and Quality with: -KB4470629 for .NET 3.5 SP1 (located in "/.NET Framework 3.5 Updates/Security and Quality Rollup") -KB4470623 for .NET 4.5.2 (located in "/.NET Framework 4.5.2 Updates/Security and Quality Rollup") -KB4470638 for .NET 4.6.x-4.7.x (located in "/.NET Framework 4.6.x-4.7.x Updates/Security and Quality Rollup") Added .NET Framework September Security Only Updates: -KB4470601 for .NET 3.5 SP1 (located in "/.NET Framework 3.5 Updates/Security Only Updates") -KB4470492 for .NET 4.5.2 (located in "/.NET Framework 4.5.2 Updates/Security Only Updates") -KB4470492 for .NET 4.6.x-4.7.x (located in "/.NET Framework 4.6.x-4.7.x Updates/Security Only Updates") Also decided to install Server 2012 on a VM where I installed all of Windows 8.0 EOL updates and searched WU for the remaining updates. This was the result: A bunch of non security updates that I didn't include on my repository! I have fixed this, so here's a more detailed list: KB3055343 - Stop error code 0xD1, 0x139, or 0x3B and cluster nodes go down in Windows Server 2012 R2 or Windows Server 2012 KB3102429 - Update that supports Azerbaijani Manat and Georgian Lari currency symbols in Windows KB3125424 - LSASS deadlocks cause Windows Server 2012 R2 or Windows Server 2012 not to respond KB3137061 - Windows Azure VMs don't recover from a network outage and data corruption issues occur KB3137726 - "VSS_E_PROVIDER_VETO" error occurs when VSS restore fails in Windows Server 2012 KB3137916 - "0x00000027" Stop error and unexpected restart in Windows Server 2012 KB3138378 - Update for Journal.dll binary in Windows KB3147071 - Connection to Oracle database fails when you use Microsoft ODBC or OLE DB Driver for Oracle or Microsoft DTC in Windows Do note that even though the description for these updates makes it seem as these are fixes specific to Server 2012 they also apply to Windows 8.0 (in some of the KB they specifically say it also applies to Windows 8 Embedded, not to mention some of the updates are also available for W7 and W8.1) There's also an important update I didn't include in the list, because I thought it is too important to not be mentioned exclusively. That is: KB3140245 - Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows As you can see, adding support to new security protocols seems important in keeping Windows 8.0 relevant and up to date. You do need to do a few extra steps to fully enable the update's functionality, so I've included a folder with everything you need in the repository. All of the updates I've mentioned so far are in the Extras folder, in case you want to install them. Available in both x64 and x86 flavors https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ
  20. Late December repository update... Just a few more days for the January patches. Replaced Monthly Rollup with the new KB4471325 (located on the root directory of the repository) Added Security Only Update, KB4471319 (located in the folder "/Security Only (Post August 2018)") Replaced Internet Explorer Cumulative Update KB4483187 (located in the folder "/Security Only (Post August 2018)") Replaced .NET Framework Security and Quality with: -KB4471102 for .NET 3.5 SP1 (located in "/NET 3.5 SP1/Security and Quality Rollup") -KB4470637 for .NET 4.5.2 (located in "/NET 4.5.2/Security and Quality Rollup") -KB4470640 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security and Quality Rollup") Added .NET Security Only Updates with: -KB4470633 for .NET 3.5 SP1 (located in "/NET 3.5 SP1/Security and Quality Rollup") -KB4470493 for .NET 4.5.2 (located in "/NET 4.5.2/Security and Quality Rollup") -KB4470500 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security and Quality Rollup") https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w This must be the first time since Vista's EOL that I've seen an update for .NET Framework 3.5 SP1. Don't forget that even if you have .NET 3.5 installed every .NET 2.0 update still applies!
  21. @someguy25 that link is old... I've been using this one for quite some time: https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ In any case, you can usually refer to my signature for the latest link (or my latest update in this thread).
  22. That option is only available in Windows 10... Looks like Steam Support just gave you a generic answer.
  23. No political subtext was meant when I wrote my reply. I may not be American, but their political squabbles can be heard and seen all around globe, so let's keep it tech only.
  24. Why do I get the feeling Microsoft is inventing solutions to problems they created in the first place? Wouldn't this categorization be useless if they just simply returned users control of the updates they installed, just like in every Windows version prior to 10? Isn't inventing an AI system that helps with major releases kinda going the long way to solve a problem that didn't need to exist in the first place? Two steps backward and one forward must be the new slogan for MS.
  25. There's the main difference. Every Windows version since 2000 (I think) has 2 main branches of updates: GDR and LDR. If you install an update normally, you default into the GDR branch, meant for general security and feature updates. If you install certain hotfixes, you're bumped into the LDR branch. This is best noted in file versions. If you're on the GDR branch, the updated files will have 6.1.6002.1xxxx version while if you're on the LDR branch the updated files will have 6.1.6002.2xxxx version. In this case, ever since the release of Windows 8.1 MS decided to kill this update approach, and as such, all updates released since around 2016 only come in the LDR flavor. Since you have the post EOL updates installed on your Vista machine, one of those updated Windows Media Player into the LDR version. If you want more info, MS made a few blog posts explaining in greater detail what I've just said: https://blogs.technet.microsoft.com/mrsnrub/2009/05/14/gdr-qfe-ldr-wth/
×
×
  • Create New...