@nicolaasjan see the reply by @abbodi1406 to this post: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-359#post-1779913 And also my reply further down: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-360#post-1780274
Thanks. I don't have this Convenience rollup update KB3125574 installed here. So I can install all Server 2008 R2 updates, including the optional ones (without the "Best Practises Analyser" updates)?
Everything is working fantastic so far. However, I have a question. I noticed this from the most recent post that it doesn't work for Windows Embedded. Is this a technical issue which makes it impossible or a workaround hasn't been created yet? Windows embedded POSReady 7 gets updates until October of 2024 and is based upon Windows 7 SP1 code base. Thanks
You need to do some reading friend! https://forums.mydigitallife.net/th...-extended-security-updates-eligibility.80606/
I'm well read. My problem was in articulating my question. What I was actually asking is it possible to apply POSReady 7 updates on Windows 7 similar to what was previously done for XP. I am presently using V12 which has allowed me to apply 2008 R2 updates on my Win 7 machine. So now with that out of the way, is there a technical problem with creating a version of BypassESU which prevents POSReady 7 updates on Win 7?
oldsh_t was being a bit sarcastic since the last 4 or 5 pages (or more) of posts are about how ESU Bypass has now been modified to install POS updates to Windows 7. EDIT: I need to read more carefully too before posting.
This post was dedicated more for Red Pill Radio. The previous BypassESU v11 supported Embedded POSReady 7 updates. There may be a complication as to how many ESU SKUID keys are enforced for POSReady 7 ESU updating. According to the CMD script for BypassESU v12 and the DLLs applied, there appears to be a temporary halt to ESU support for Embedded POSReady 7 - only Server 2008 R2 x64 and Embedded 7 Standard x86 and x64 ESU updates are supported (this is at least from examining the initial release from February 2023, I can't say whether there have been amendments to it and a new re-released version of BypassESU-v12 on its download page.) Another handy way around to installing ESU updates for WIndows 7 is using the W7ESUI v0.4 Installer script - it requires downloading the Windows Embedded 7 x86/x64 or Windows Server 2008 R2 x64 security updates packages from the Microsoft Update Catalog (Use the search as "2023-04" for the upcoming April 2023 security updates due for release on April 11th/April 12th). Be mindful what version of Windows 7 you are using for choosing and downloading your relevant security update packages - a 32-bit (x86) or 64-Bit (x64). First, place that W7ESUI v0.4 folder with the installer scripts on a drive that can comply easily with DOS commands (eg. C:\W7ESUI04\ or D:\W7ESUI04\) Place a copy of those packages (one at a time) into that W7ESUI v0.4 folder, and "extract" the contents of that .MSU package using 7-Zip. Then, run the CMD script with the "Run As Administrator" privilege. If all looks ready and satisfied, press 0 to begin or press 9 to exit. This method (ie. using 7-Zip to "extract" the .CAB packages content inside the .MSU packages) is especially handy when the security update .MSU package refuses to open due to a pre-check from that MSU installer package that the BypassESU v1x scripting has not mitigated around yet. I've yet to personally try to install an Embedded POSReady 7 security update since I'm using an x86 version of Windows 7 so for now I'm making use of installing the ESU Windows Embedded 7 Standard security updates.
A few reasons this may happen, and I'll add some of the basic ones that trick a lot of us: 1) The time clock on your PC (at the bottom right of the taskbar) is not synchronized with Microsoft's. You have to open it and select "Change date and time settings" => Check that your time zone details for your geographical region location are correct before selecting the "Internet Time" tab => Select "Change settings" => Make sure you've ticked the "Synchronize with an Internet time server" box, the server selected is "time.windows.com" => (At this point, be connected to the internet) Press the "Update now" button. If the first attempt fails, wait a few seconds or up to 1 minute before pressing again the "Update now" button. Once you receive your "The clock was successfully synchronized with time.windows.com on dd/mm/yyyy at xx:xx (AM/PM)." message, you can press the "OK" buttons to close these settings. 2) Some of the files necessary for logging of Windows Updates are heavily fragmented, and the C: drive is maybe due for disk defragmentation. You can use the one provided with Windows (which may take hours to complete if your CPU includes an L3 cache - a high end DDR2 memory RAM PC/notebook can whip this process in 30 minutes or less!), or a freeware third-party defragger like Piriform's Defraggler (the last version released was v2.22.995). In the "File List" tab once completing an analysis, you can manually select ALL files to defragment, else order them by their properties tabs for their file locations, file sizes (this option would be better, as you can un-tick the very large size files which will slow down the defragmentation work of all the smaller files. The large files you best select singularly on an individual basis.) In particular, it's the CBS.log file that can become heavily fragmented, so it is this file that needs to be a priority for defragmentation. Maybe also the WindowsUpdate.log file. Take note that the system files in the Windows directory are prone to fragmentation over time from usage and updates, so these also best be defragmented to assure better response on your PC. 3) DataStore corruption in Windows Updates. Sometimes this happens and it really hampers on checking for updates. One of the best tools to set your PC system straight is to deploy the System Update Readiness Tool (KB947821-v34) [Released in October 2014]. Running this tool checks over your update history and makes corrections to misconfigurations, etc in Windows, Windows Update, and maybe also rebuilds the DataStore and CBS.log file. It takes over 30 minutes to an hour pending on your PC's hardware specifications, but it's worthwhile in the long run. This is probably a very reliable solution to other system issues, as afterwards you may have listed in Windows Updates particular updates that need to be re-installed (as their original contents were corrupted at some past time.) 4) You may try to get hold of Microsoft's Fix It (if it can still be available somewhere - I still have it intact), or a suitable MS Fix It hotfix solution to an error code involving Windows Update, etc. Otherwise, maybe a third-party utility like The Windows Club's "Fix WU Utility v1.0" or "FixWin Utility v1.2" (which includes an easy way to run the system file check utility). After running Option 3), I would recommend running the Defraggler again to check and defragment system files that were repaired by the System Update Readiness Tool. These options I've listed will not cause the havoc involved commonly experienced after suggesting to delete the C:\Windows\SoftwareDistribution folder. This delete the folder method is a quick-and-easy fix, yet it maybe takes 3 hours or more to fix the update history back up to normal again. Good luck.
thanks for the help, it probably had something to do with the datastore, it updated in the end. if i have more problems i will try the System Update Readiness Tool
Hello everybody, thank you for this wonderful tool. May Windows 7 live for many more years. I stumbled into a problem running the latest Bypass 12_u. Windows 7 Pro 64. Updated to Jan 2020 plus the required ESU updates. I followed the instructions and double checked everything. When I run the Application (LiveOS-Setup) as admin I get this error message: Bin\AMD_64********34506a8b67a.manifest is missing Inside Bin folder there is file called AMD_64********34506a8b.man. It looks to me the last couple of letters in the file name are different/missing. I did some search on this thread and found a couple of guys reported the same problem. No solution. Help please.
Hello Elw00d, Where exactly did you download your Bypass 12_u? The host for BypassESU v12 is on a Windows 7 forum webpage at a Deutsch website called d e s k m o d d e r (I'm sorry I can't give you the direct link as I haven't posted enough messages here.) You can enter the details below in your search engine for the webpage: windows-7-erweiterte-sicherheitsupdates-esu-erhalten-wird-moeglich-sein Just to verify your claim, I downloaded it again and unzipped the package contents with 7-Zip (the package password is "2023"). In the "bin" folder, the manifest files were indeed there and with their full respective filenames: "amd64_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.3.9603.30600_none_6022b34506a8b67a.manifest", and "x86_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.3.9603.30600_none_040417c14e4b4544.manifest". As long as you've unpacked the contents in a folder that is not inside too many other folder layers (like on the Desktop or in the Downloads or My Documents folders), the file name lengths remain intact.