- #WINDOWS NT 6.1 ISO HOW TO#
- #WINDOWS NT 6.1 ISO INSTALL#
- #WINDOWS NT 6.1 ISO UPDATE#
- #WINDOWS NT 6.1 ISO MANUAL#
- #WINDOWS NT 6.1 ISO WINDOWS 10#
I have attached my batch script (and also a VBS script I found which can detect and hide the EOSNotify standalone updates if they are pending).
#WINDOWS NT 6.1 ISO HOW TO#
I hope this is useful to help you find out how to remove EOSNotify from Windows 7 to prevent End Of Support notification nag screen, and I welcome any feedback anyone may have regarding my script which will help you to automate the process. I have tested the batch script extensively on my systems but I suggest that you review the contents of it carefully to make sure you are OK with what it does to your installation(s) before you run it/integrate it into your ISO. However, as nuhi points out I think it is important that the user has the choice wether or not to completely remove EOSNotify or to simply disable it from running, as there are pro's and con's of each solution. I welcome anyone to use the information I have gathered here to enable them to clean up Windows 7 installations, it would benefit the community greatly.
#WINDOWS NT 6.1 ISO UPDATE#
It would be great if this functionality could be integrated by nuhi into NTLite by Nlitesoft and other tools like WSUS Offline Update by Torsten Wittrock, for example. I suggest the script can be run to set these flags before any updates are applied to a fresh install, to prevent the prompt(s) from appearing. My script sets the "DisableGwx" and "DisableOSUpgrade" opt-out flags in the registry as recommended at the original release back in 2016, in addition to setting "DiscontinueEOS" and "Discontinue" opt-out flags in the registry as recommended by Microsoft in KB4524752 in Oct 2019. I run it both before applying updates (to block notifications) and afterwards (to remove the application). Blocking the standalone updates is not enough.įor doing that on my systems I have compiled this batch script which removes EOSNotify program from the SxS sub-system manifest and also the related scheduled tasks. So, given that EOSNotify is now included in other updates which cannot be avoided, the only option is to remove the EOSNotify application after it installed.
#WINDOWS NT 6.1 ISO WINDOWS 10#
(Note, I have also tried using the KB3125574 Convenience rollup update for Windows 7 SP1 (originally released in 2016) and although that update did not include EOSNotify, it's prerequisits packages (the SSU) did inlcude GWX (the Get Windows 10 application), so I have avoided it.) HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-eosnotify_31bf3856ad364e35_none_cf9552e0f1896db2 There is only one entry in the registry, which is: You should NOT exclude/remove the latter two Security-only updates from your ISO because they also contain important (security) patches!Įach of the above updates have a different varient of the EOSNotify SxS module manifest, these are:Īmd64_microsoft-windows-eosnotify_31bf3856ad364e35_.18067_none_41b0929ee4b7e75eĪmd64_microsoft-windows-eosnotify_31bf3856ad364e35_.22194_none_4216bec7fdf08ef6Īmd64_microsoft-windows-eosnotify_31bf3856ad364e35_.24541_none_44301f27faf12bb3Īmd64_microsoft-windows-eosnotify_31bf3856ad364e35_.24544_none_44332005faee77b8 KB4524752 OctoWindows 7 SP1 support notification for Windows 7 Professional KB4493132 OctoWindows 7 SP1 support notification for Windows 7
#WINDOWS NT 6.1 ISO INSTALL#
To date 1 (after the End Of Support for Windows 7 on 1), I have counted 4 updates which install EOSNotify while using WSUS Offline Update to install Security-Only updates onto a fresh installation of Microsoft Windows 7 Pro SP1 x Official ISO, they are: There are some files still remaining because there is more than one SxS module installed for the Windows 7 End Of Service Notifier application (EOSNotify). We are interested in the complete option as well of course, not everyone is for that, pros and cons for both sides - my goal as mentioned before is to have both.Įither way please let the tone slides next time, very valuable member like yourself and I don't mind the occasional bump against the closed source or going too deep.
#WINDOWS NT 6.1 ISO MANUAL#
Kasual, thanks, just to add that abbodi86 is used to the scripting world where admins take full control over the manual config and cannot afford 3rd party mistakes on the machines - so less changes the better in those cases. I prefer removing the unused files and upgrading with trimmed ISOs (self-upgrade mode, aka host refresh), don't need to worry if the latest update re-enabled anything. It is my goal that both options are available tricky environment goes with config and MS engines only, home/enthusiast can go further and remove the files as well. Toomuchpie, thanks for the suggestion, will be done in the next update.Ībbodi86, thanks for the heads up on the tweak as well.