Jump to content

Search the Community

Showing results for tags 'windows 7'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Categories

  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions

Categories

  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

  1. Microsoft has released its Patch Tuesday updates for Windows 8.1 (KB5020023) and Windows 7 (KB5020000). To get the Windows 7 update, you will need to be a customer that has purchased the Extended Security Update (ESU). Windows 8.1/7 Improvements Addresses a Distributed Component Object Model (DCOM) authentication hardening issue to automatically raise authentication level for all non-anonymous activation requests from DCOM clients. This will occur if the authentication level is less than RPC_C_AUTHN_LEVEL_PKT_INTEGRITY. Updates the daylight-saving time (DST) for Jordan to prevent moving the clock back 1 hour on October 28, 2022. Additionally, changes the display name of Jordan standard time from “(UTC+02:00) Amman” to “(UTC+03:00) Amman”. Addresses an issue where Microsoft Azure Active Directory (AAD) Application Proxy Connector cannot retrieve a Kerberos ticket on behalf of the user because of the following general API error: “The handle specified is invalid (0x80090301).” Addresses an issue where, after installing the January 11, 2022 or later update, the Forest Trust creation process fails to populate the DNS name suffixes into the trust information attributes. Addresses an issue where the Microsoft Visual C++ Redistributable Runtime does not load into the Local Security Authority Server Service (LSASS) when Protected Process Light (PPL) is enabled. Addresses security vulnerabilities in the Kerberos and Netlogon protocols as outlined in CVE-2022-38023, CVE-2022-37966, and CVE-2022-37967. For deployment guidance, see the following articles: KB5020805: How to manage the Kerberos protocol changes related to CVE-2022-37967 KB5021130: How to manage the Netlogon protocol changes related to CVE-2022-38023 KB5021131: How to manage the Kerberos protocol changes related to CVE-2022-37966 Known issues (Windows 8.1) Symptom Next step After this update or a later Windows update is installed, domain join operations might be unsuccessful and error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" occurs. Additionally, text stating "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy" might be displayed. Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain. For more information about this issue, see KB5020276—Netjoin: Domain join hardening changes. Note Consumer Desktop editions of Windows are unlikely to experience this issue. We have added guidance to KB5020276 and are evaluating whether optimizations can be made in a future Windows Update. This guidance will be updated as soon as those changes are released. Known issues (Windows 7) Symptom Next Step After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. After this update or a later Windows update is installed, domain join operations might be unsuccessful and error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" occurs. Additionally, text stating "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy" might be displayed. Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain. For more information about this issue, see KB5020276—Netjoin: Domain join hardening changes. Note Consumer Desktop editions of Windows are unlikely to experience this issue. We have added guidance to KB5020276 and are evaluating whether optimizations can be made in a future Windows Update. This guidance will be updated as soon as those changes are released. The updates will be delivered via Windows Update but if you need to download them to install offline, you can grab them from the Microsoft Update Catalog (Windows 8.1/Windows 7). Patch Tuesday updates for Windows 8.1 (KB5020023) and Windows 7 (KB5020000)
  2. Microsoft plans to end extended Windows 7 support in the first half of 2023, which means no more paid security updates for those unwilling to upgrade to newer versions. The death of Windows 7 also implies the end of support for mainstream browsers, such as Chrome, Edge, and Firefox. Google recently announced plans to stop updating Chrome on Windows 7 and 8.1 in early 2023, but Mozilla has yet to decide when to pull the plug. According to a post on Bugzilla (via gHacks), the browser's developers are considering two options: end support in the first quarter of 2023 or keep updating Firefox on the old Windows versions until August 2023, when the browser will move to a newer Extended Support Release version. The development team says that ditching Firefox for Windows 7 and 8.1 in early 2023 could make their lives a bit easier by removing the need for Windows 7 test automation machines. At the same time, keeping them running for a little longer "is not the end of the world," considering that Firefox still has "a lot of users on Windows 7." According to the latest data from Statcounter, Windows 7 holds almost 10% of the PC market. It is worth mentioning that running an unsupported browser on an unsupported Windows version will not cause your computer to explode, as shown by people still using Windows XP in 2022. Still, accessing the modern internet using software that no longer receives security updates is not the best idea. Those sticking to Windows 7 should get ready to kiss their favorite operating system goodbye and move on to a supported OS with supported browsers. Mozilla is considering extending Firefox support on Windows 7 and 8.1
  3. If your devices are still running Windows 7 or 8.1, listen up: according to a recent announcement by Google, the company will officially end Chrome support for the two aforementioned operating systems in line with the tentative release of Chrome 110 on February 7, 2023. While Google Chrome will continue working after the update, it will no longer receive any feature updates and security patches on devices running these OSs. This increases users' and businesses' risks of falling prey to online attacks if they continue to use Windows 7 or 8.1. "You’ll need to ensure your device is running Windows 10 or later to continue receiving future Chrome releases," Google states in its Chrome Help Blog. "This matches Microsoft’s end of support for Windows 7 ESU and Windows 8.1 extended support on January 10th, 2023." Windows 7, which reached its end of support back in January 2020, still has a 10.68% desktop market share worldwide, according to StatCounter. This means that there are still many people worldwide using the OS. Windows 8.1, on the other hand, holds a measly 2.7% market share. Given that more apps are dropping support for the two OSs aside from Chrome, it's best for users to finally upgrade to Windows 10 and 11. Source: Google via AndroidAuthority Google Chrome is dropping support for Windows 7 and 8.1 in February 2023
  4. Windows 7 and Windows Server 2008 R2 will get at least an additional 2 years of security updates, courtesy of the micro-patching solution 0Patch. Microsoft introduced Extended Security Updates for Windows 7 and Windows 2008 R2 when the operating systems ran out of support more than 2 years ago. Organizations could subscribe to ESU to receive security updates for these devices, but ways were soon discovered to install these patches on home devices running Windows 7 as well. The last batch of security updates will arrive in January 2023 for Windows 7. Microsoft announced already that it won't extend support beyond the promised three years. For Server 2008 R2, Microsoft plans to extend support by a year. Windows 7's usage share has dropped significantly in the years since support ended. It has been replaced by Windows 10 for the most part, but there is still a sizeable number of devices that use the classic operating system. source 0Patch 0Patch announced this week that it will provide its micro-patching service until January 2025, at least, for Windows 7 and Windows Server 2008 R2 devices. The company produces security patches for "the most-likely-to-be-exploited critical vulnerabilities". We have decided to keep providing security patches for Windows 7 and Windows Server 2008 R2 for critical vulnerabilities that are likely to get exploited, and will be happy to keep you secured for a fraction of what you had paid for ESU so far. And you won't have to restart your computer even once, because our patches are applied directly in the memory of running processes instead of changing your executable files! The service comes at a cost, but it is cheaper than what Microsoft charged for its ESU updates. Pro and Enterprise plans are available for 24.95€ or 34.95€ per year and agent (about the same in US Dollar). Both plans include patches for Microsoft Office 2010 as well. Devices with Windows 7 or Windows Server 2008 R2 that have not been updated since 2020 may also subscribe to 0Patch to receive all micro patches the company released since 2020 and all future updates. A total of 52 critical security issues were patched by the company since 2020. 0Patch focuses on critical security issues that are the most likely to be exploited. Closing Words Windows 7 users who plan to continue running the system may sign-up for 0Patch's Pro plan to get another two years of security updates out of the system. One has to remember that 0Patch focuses on critical patches only, but considering that there is no other option available, it may be a good investment. Now You: which operating systems do you devices run? (via Born) 0Patch promises 2 additional years of security patches for Windows 7 and Server 2008 R2
  5. Microsoft has released its Patch Tuesday updates for Windows 8.1 (KB5018474) and Windows 7 (KB5018454). To get the Windows 7 update, you will need to be a customer that has purchased the Extended Security Update (ESU). The improvements this month for both versions of Windows are the same, they are as follows: Improvements This cumulative security update contains improvements that are part of update KB5017361 (Windows 7) / KB5017367 (Windows 8.1) (released September 13, 2022) and includes key changes for the following: Addresses an issue that leads to User Datagram Protocol (UDP) packet drops from Linux virtual machines (VMs). Updates daylight saving time (DST) in Chile to start on September 11, 2022 instead of September 4, 2022. For more information about the resolved security vulnerabilities, please refer to the Deployments | Security Update Guide and the October 2022 Security Updates. Known Issues (Windows 7) Symptom Next step After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. After installing this update, file copies which use Group Policy Preferences might fail or might create empty shortcuts or files that have 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration > Preferences > Windows Settings in Group Policy Editor. To mitigate this issue, do ONE of the following: Clear the "Run in logged-on user's security context (user policy option)" check box. Note This might not mitigate the issue for items that use a wildcard (*). In the affected Group Policy, change "Action" from "Replace" to "Update". If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotation marks) from the destination might allow the copy to be successful. We are working on a resolution and will provide an update in an upcoming release. Known Issues (Windows 8.1) Symptoms Next step After installing this update, file copies which use Group Policy Preferences might fail or might create empty shortcuts or files that have 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration > Preferences > Windows Settings in Group Policy Editor. To mitigate this issue, do ONE of the following: Clear the "Run in logged-on user's security context (user policy option)" check box. Note This might not mitigate the issue for items that use a wildcard (*). In the affected Group Policy, change "Action" from "Replace" to "Update". If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotation marks) from the destination might allow the copy to be successful. We are working on a resolution and will provide an update in an upcoming release. Both of the updates will be available for their respective systems through Windows Update. If you need to download them for an offline installed, then you can get them from the Microsoft Update Catalog (Windows 7 update, Windows 8.1 update). Windows 8.1 (KB5018474) and Windows 7 (KB5018454) Patch Tuesday updates arrive
  6. Microsoft has released its Patch Tuesday updates for Windows 8.1 (KB5017367) and Windows 7 (KB5017361). Both updates include improvements and issues for their respective Windows versions, but luckily, the issues have workarounds outlined, so you can get around the problems. Windows 8.1 Improvements This cumulative security update includes improvements that are part of update KB5016681 (released August 9, 2022) and includes key changes for the following issue: This update contains miscellaneous security improvements to internal OS functionality. No specific issues are documented for this release. For more information about the resolved security vulnerabilities, please refer to the Deployments | Security Update Guide and the September 2022 Security Updates. Known issues in this update Symptoms Next step Starting at 12:00 A.M. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by the Chilean government about a daylight saving time (DST) time zone change. This moves the DST change which was previously September 4 to September 10. Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022: Time shown in Windows and apps will not be correct. Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off. Automation that uses date and time, such as Scheduled tasks, might not run at the expected time. Timestamp on transactions, files, and logs will be 60 minutes off. Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources. Windows devices and apps outside of Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device. To mitigate this issue, please see Possible issues caused by new Daylight Savings Time in Chile. We are working on a resolution and will provide an update in an upcoming release. Note We plan to release an update to support this change; however, there might be insufficient time to properly build, test, and release such an update before the change goes into effect. Please use the workaround above. Windows 7 Improvements This cumulative security update contains improvements that are part of update KB5016676 (released August 9, 2022) and includes key changes for the following issue: This update contains miscellaneous security improvements to internal OS functionality. No specific issues are documented for this release. For more information about the resolved security vulnerabilities, please refer to the Deployments | Security Update Guide and the September 2022 Security Updates. Known issues in this update Symptom Next step After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. Starting at 12:00 A.M. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by the Chilean government about a daylight saving time (DST) time zone change. This moves the DST change which was previously September 4 to September 10. Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022: Time shown in Windows and apps will not be correct. Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off. Automation that uses date and time, such as Scheduled tasks, might not run at the expected time. Timestamp on transactions, files, and logs will be 60 minutes off. Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources. Windows devices and apps outside of Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device. To mitigate this issue, please see Possible issues caused by new Daylight Savings Time in Chile. We are working on a resolution and will provide an update in an upcoming release. Note We plan to release an update to support this change; however, there might be insufficient time to properly build, test, and release such an update before the change goes into effect. Please use the workaround above. Both of these updates are available through Windows Update. Note that on Windows 7, you must be an Extended Security Update (ESU) customer to get this update. If you need to download these updates for installation on an offline machine, you can download them from the Microsoft Update Catalog: Windows 8.1 (KB5017367) and Windows 7 (KB5017361). Windows 8.1 (KB5017367) and Windows 7 (KB5017361) get September Patch Tuesday updates
  7. Microsoft has released its Patch Tuesday updates for Windows 7 (KB5016679) and Windows 8.1 (KB5016683). They both contain pretty much the same improvements, however, the Windows 8.1 notes do not list any known issues. It’s important to note that only Windows 7 users who have purchased extended security update (ESU) support will receive the update. Improvements (applies to Windows 7 and Windows 8.1) This security-only update includes new improvements for the following issue: Addresses an issue in which Speech and Network troubleshooters will not start. Addresses an issue that might cause the Local Security Authority Server Service (LSASS) to leak tokens. This issue affects devices that have installed Windows updates dated June 14, 2022 or later. This issue occurs when the device performs a specific form of service for user (S4U) in a non-Trusted Computing Base (TCB) Windows service that runs as Network Service. Enforces a hardening change that requires printers and scanners that use smart cards for authentication to have firmware that complies with section 3.2.1 of RFC 4556. If they do not comply, Active Directory domain controllers will not authenticate them. Mitigations that allowed non-compliant devices to authenticate will not exist after August 9, 2022. For more information about this change, see KB5005408. For more information about the resolved security vulnerabilities, please refer to the Deployments | Security Update Guide and the August 2022 Security Updates. Known issues in this update (Windows 7 only) Symptom Next step After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. This Windows 7 update is not available via Windows Update. The best way to get it would be to download it through the Microsoft Update Catalog. The Windows 8.1 update is also unavailable via Windows Update, but you can grab that via Microsoft Update Catalog too. Microsoft releases Windows 7 (KB5016679) and Windows 8.1 (KB5016683) Patch Tuesday updates
  8. Nvidia stopped issuing GPU drivers updates to systems running Windows 8 and 7 in late 2021. Still, the company promised to release periodical security patches to unsupported devices until September 2024. One such update has just become available to those refusing to upgrade to Windows 10 or 11. Driver 473.81 is available only to systems running Windows 7 and 8, and it contains no new features or game-related fixes. According to the release notes, the driver brings only security patches, and all the details will soon be available on the Nvidia Product Security Page. Nvidia says users with supported hardware need to update to Windows 10 and 11 to receive performance enhancements, new features, bugfixes, and game-specific improvements. Hardware-wise, Nvidia GeForce 473.81 driver supports desktop graphics cards from the GTX 600 to RTX 3000 Series and mobile GPUs from the GeForce 800 Series to RTX 3000 Series. Users can download the latest release from the official Nvidia website. On the AMD side, owners of older Radeon GPUs received an unofficial driver that enables AMD's latest AI-based noise suppression technology. Official drivers allow using the new tech only on the Radeon 6000 Series, but you can get it using a third-party driver from NimeZ without investing into a new graphics card. Nvidia issues driver security update for unsupported systems with Windows 7 and 8
  9. Microsoft ended support for its Windows 7 operating system in 2020. The company offers extended support to organizations and businesses, but not to Home customers. Microsoft's initial plan was to limit extended support to three years after support end, but it appears that the company could extend support by another three years, making it six years in total. Our colleagues over at Deskmodder report that the July security updates KB5015861 and KB5015862 include the required ESU licenses and keys to extend support beyond the first three years. The second extension would guarantee support of Windows 7 until January 2026. Microsoft creates updates for the following Windows 7 editions as part of the extended security updates program: Windows 7 SP1 Enterprise Windows 7 SP1 Pro Windows Server 2008 R2 Windows Embedded Standard 7 Windows Embedded POS Ready 7 Microsoft released the monthly and security-only cumulative updates for Windows 7 ESU systems as part of the July 2022 Patch Day. ESU updates can only be installed officially on licensed machines. Bypasses exist to install Microsoft's official updates on Windows 7 Home devices, including Windows 7 Home and Professional. Microsoft has not confirmed or denied the extension of Windows 7 ESU. Windows 7 holds a sizeable share of the desktop operating system market. Statcounter, one of the third-party companies that is tracking usage statistics, sees it at 11.54% of the Windows market share. Windows 11, Microsoft's newest operating system, sits at 10.96%, which makes Windows 7 the second most used version of Windows according to the company. It makes sense to extend support if the numbers are close to real usage numbers. Organizations may require more time to move to a new version of Windows, or another operating system. The extension gives organizations that time. Organizations who have devices with ESU can protect the devices for another three years. Microsoft announced earlier this month that it won't provide Windows 8.1 customers with a similar offer. Windows 8.1's usage share is less than 3% according to Statcounter, even though it is still officially supported. If Windows 7 support is extended by another three years, it would mean that the operating system will be supported for longer than its direct successor, Windows 8.1, and even Windows 10. Both operating systems will run out of support before 2026. Microsoft could offer support extensions for Windows 10, the most used version of Windows at the time of writing. Now You: what is your take on this? It looks as if Microsoft could extend Windows 7 Support by another three years
  10. Microsoft has released Patch Tuesday updates for Windows 8.1 (KB5015874) and Windows 7 (KB5015861). They each come with a whole host of improvements and known issues with workarounds. It’s worth noting that support for Windows 8.1 will end in January, so Microsoft urges you to upgrade to a later edition of Windows. The Patch Tuesday update for Windows 7 requires you to have purchased the Extended Security Update (ESU) support. Windows 8.1 Improvements Starting with this release, we are displaying a dialog box to remind users about the End of Support (EOS) for Windows 8.1 in January 2023. If you click Remind me later, the dialog box will appear once every 35 days. If you click Remind me after the end of support date, the dialog box will not appear again until after the EOS date. This reminder does not appear on the following: Managed Pro and Enterprise devices. Windows Embedded 8.1 Industry Enterprise and Windows Embedded 8.1 Industry Pro devices. When you use Encrypting File System (EFS) https://docs.microsoft.com/windows/win32/fileio/file-encryption files over a remote Web Distributed Authoring and Versioning (WebDAV) protocol connection, the connection might be unsuccessful. NTLM authentication through an external trust is unsuccessful when serviced by a domain controller that has the January 11, 2022 or later Windows update installed. This issue occurs if the DC is in a non-root domain and does not hold the global catalog (GC) role. Impacted operations may log the following errors: The security database has not been started. The domain was in the wrong state to perform the security operation. 0xc00000dd (STATUS_INVALID_DOMAIN_STATE) Applications might not run after an AppLocker publisher rule is deployed. Addresses a known issue that might prevent you from using the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the Internet after a client device connects. Addresses a known issue in which Windows Servers that use the Routing and Remote Access Service (RRAS) might be unable to correctly direct Internet traffic. Devices which connect to the server might not connect to the Internet, and servers can lose connection to the Internet after a client device connects. Known issues in this update Symptom Next step Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. We are working on a resolution and will provide an update in an upcoming release. Windows 7 Improvements When you use Encrypting File System (EFS) files over a remote Web Distributed Authoring and Versioning (WebDAV) protocol connection, the connection might be unsuccessful. NTLM authentication through an external trust is unsuccessful when serviced by a domain controller that has the January 11, 2022 or later Windows update installed. This issue occurs if the DC is in a non-root domain and does not hold the global catalog (GC) role. Impacted operations may log the following errors: The security database has not been started. The domain was in the wrong state to perform the security operation. 0xc00000dd (STATUS_INVALID_DOMAIN_STATE) Addresses a known issue that might prevent you from using the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the Internet after a client device connects. Addresses a known issue in which Windows Servers that use the Routing and Remote Access Service (RRAS) might be unable to correctly direct Internet traffic. Devices which connect to the server might not connect to the Internet, and servers can lose connection to the Internet after a client device connects. Known issues in this update Symptom Next step After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. We are working on a resolution and will provide an update in an upcoming release. Both of these updates are now available to download through Windows Update if you’re eligible. Your systems will download and install the updates automatically. Windows 8.1 (KB5015874) and Windows 7 (KB5015861) Patch Tuesday updates land
  11. One year ago, AMD released the first Radeon Software driver without official Windows 7 support. Starting with version 21.6.1, you need Windows 10 and newer to run the most recent AMD drivers. Still, sometimes developers release unplanned updates to fix specific issues or security bugs in unsupported products. That is what happened to driver 22.6.1 that AMD has now released for systems running the good-old (and now deceased) Windows 7. AMD Radeon Software 22.6.1 focuses on fixing a single Windows 7-related bug: AMD Radeon™ Software may fail to install on some AMD Graphics Products such as the Radeon™ RX 6900 XT. The company also warn users about two known issues in driver 22.6.1: Enhanced Sync may cause a black screen to occur when enabled on some games and system configurations. Any users who may be experiencing issues with Enhanced Sync enabled should disable it as a temporary workaround. Radeon performance metrics and logging features may intermittently report extremely high and incorrect memory clock values. Note that today's release is available only for systems with Windows 7. The most recent update for computers with Windows 10 and 11 is version 22.5.2. Download AMD Software: Adrenalin Edition 22.6.1 Driver for Windows 7 64-bit Download AMD Software: Adrenalin Edition 22.6.1 Driver for Windows 7 64-bit (AMD Radeon RX 6400 and Radeon RX 6500 XT only) AMD releases driver 22.6.1 to fix a single issue on Windows 7
  12. Microsoft has released the June Patch Tuesday updates for Windows 7 (KB5014742) and Windows 8.1 (KB5014746). Both updates bring improvements to their respective operating systems but also carry issues that you may have to use a workaround on. Without further ado, here’s what’s new. Windows 7 Improvements This security-only update includes new improvements for the following issue: Printing to a NUL port from a Low Integrity Level (LowIL) process application could cause printing failures. Known issues Symptom Next step After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. We are working on a resolution and will provide an update in an upcoming release. Windows 8.1 Improvements This security-only update includes new improvements for the following issue: Printing to a NUL port from a Low Integrity Level (LowIL) process application could cause printing failures. Addresses an elevation of privilege (EOP) vulnerability under CVE-2022-30154 for the Microsoft File Server Shadow Copy Agent Service. To become protected and functional, you must install the June 14, 2022 or later Windows update on both the application server and the file server. The application server runs the Volume Shadow Copy Service (VSS)-aware application that stores data on the remote Server Message Block 3.0 (or higher) shares on a file server. The file server hosts the file shares. If you don’t install the update on both machine roles, backup operations carried out by applications, which previously worked, might fail. For such failure scenarios, the Microsoft File Server Shadow Copy Agent Service will log FileShareShadowCopyAgent event 1013 on the file server. For more information, see KB5015527. Known issues Symptom Next step Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. We are working on a resolution and will provide an update in an upcoming release. Unlike the Windows 11 and Windows 10 updates which will be delivered through Windows Update, the updates for Windows 7 (download) and Windows 8.1 (download) are best being manually downloaded as they won’t come through Windows Update. You can also configure Windows Server Update Services to get the updates. Windows 7 (KB5014742) and Windows 8.1 (KB5014746) June Patch Tuesday updates arrive
  13. Microsoft has released the Patch Tuesday update for Windows 8.1 (KB5014011) and Windows 7 (KB5014012) today as it’s the second Tuesday of the month. Installing them will protect your system against certain vulnerabilities but both also come with known issues. Here’s what each release contains and their known issues. Windows 8.1 Improvements This cumulative security update contains improvements that are part of update KB5012670 (released April 12, 2022) and includes new improvements for the following issues: The Key Distribution Center (KDC) code incorrectly returns error message KDC_ERR_TGT_REVOKED during Domain Controller shutdown. After installing the January 2022 Windows update or a later Windows update on the Primary Domain Controller emulator (PDCe), listing or modifying name suffixes routing by using Netdom.exe or "Active Directory Domains and Trusts" snap-in may fail and you receive the following error message: "Insufficient system resources exist to complete the requested service." The Primary Domain Controller (PDC) for the root domain incorrectly logs warning and error events in the System log when trying to scan outbound-only trusts. Known issues in this update Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release. After installing updates released January 11, 2022 or later updates, apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. To resolve this issue manually, apply the out-of-band updates for the version of .NET Framework used by the app. Windows 7 Improvements This cumulative security update contains improvements that are part of update KB5012626 (released April 12, 2022) and includes new improvements for the following issues: The Key Distribution Center (KDC) code incorrectly returns error message KDC_ERR_TGT_REVOKED during Domain Controller shutdown. After installing the January 2022 Windows update or a later Windows update on the Primary Domain Controller emulator (PDCe), listing or modifying name suffixes routing by using Netdom.exe or "Active Directory Domains and Trusts" snap-in may fail and you receive the following error message: "Insufficient system resources exist to complete the requested service." The Primary Domain Controller (PDC) for the root domain incorrectly logs warning and error events in the System log when trying to scan outbound-only trusts. Known issues in this update Symptom Workaround After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release. You can get these updates through Windows Update or download them manually: Windows 8.1 KB5014011, Windows 7 KB5014012. May's Patch Tuesday updates for Windows 8.1 (KB5014011) and Windows 7 (KB5014012) out now
  14. Aside from Windows 10 and Windows 11, Microsoft has released Patch Tuesday updates for its two older systems, Windows 7 (KB5012626) and 8.1 (KB5012670). Unlike the Windows 11 patch notes, the ones for Windows 7 and Windows 8.1 are quite extensive and so are the known issues. Windows 8.1 Improvements and fixes Addresses an issue in Windows Media Center where some users might have to reconfigure the application on each start. Addresses a memory leak that was introduced by the PacRequestorEnforcement registry key in the November 2021 Cumulative Update that causes a decrease in performance on domain controllers. Addresses an issue in which Event ID 37 might be logged during certain password change scenarios. Addresses an issue in which Windows might go into BitLocker recovery after a servicing update. Addresses an issue in which domain joins may fail in environments that use disjoint DNS hostnames. Addresses an issue that causes a Denial of Service vulnerability on Cluster Shared Volumes (CSV). For more information, see CVE-2020-26784. Addresses an issue that prevents you from changing a password that has expired when you sign in to a Windows device. Known issues in this update Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release. After installing updates released January 11, 2022 or later updates, apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. Note for developers: Affected apps use the System.DirectoryServices API. To resolve this issue manually, apply the out-of-band updates for the version of .NET Framework used by the app. Note These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. Windows 7 Improvements and fixes Addresses an issue in Windows Media Center where some users might have to reconfigure the application on each start. Addresses a memory leak that was introduced by the PacRequestorEnforcement registry key in the November 2021 Cumulative Update that causes a decrease in performance on domain controllers. Addresses an issue in which Event ID 37 might be logged during certain password change scenarios. Addresses an issue that occurs when you try to write a service principal name (SPN) alias (such as www/contoso) and HOST/NAME already exists on another object. If the user has the RIGHT_DS_WRITE_PROPERTY on the SPN attribute of the colliding object, you receive an “Access Denied” error. Addresses an issue in which domain joins may fail in environments that use disjoint DNS hostnames. Addresses an issue that prevents you from changing a password that has expired when you sign in to a Windows device. Known issues in this update Symptom Workaround After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release. The Windows 8.1 update will be updated automatically through Windows Update while the Windows 7 update will be installed automatically through Windows Update if you are an ESU customer. Microsoft releases Patch Tuesday updates for Windows 7 (KB5012626) and 8.1 (KB5012670)
  15. Patch Tuesday: Here's what's new for Windows 7 and 8.1 this month Today is the second Tuesday of May, and that means it's time for this month's Patch Tuesday. Microsoft is rolling out cumulative updates for all supported versions of Windows, and that includes Windows 8.1 and Windows 7. Keep in mind, Windows 7 actually reached end of support earlier this year, so you'll only be getting updates if you're a business user paying for extended security updates. These monthly updates come in two flavors - monthly rollup and a security-only update - and by default, you'll get the monthly rollup automatically. For Windows 8.1 and Windows Server 2012 R2, the monthly rollup update is KB4556846, and you can download it manually here, though you can also get it through Windows Update. It includes the following changes: Updates the 2020 start date for daylight saving time (DST) in the Kingdom of Morocco. For more information, see KB4557900. Addresses an issue that causes offline file syncing to stop responding or fail in mobsyc.exe. Security updates to Internet Explorer, the Microsoft Scripting Engine, Windows App Platform and Frameworks, Windows Input and Composition, Windows Media, Windows Kernel, Windows Core Networking, Internet Information Services, Windows Network Security and Containers, Windows Active Directory, the Microsoft JET Database Engine, and Windows Storage and Filesystems. The update has no known issues. As for the security-only update, it's labeled as KB4556853 and you can download it manually here. This one won't be sent out through Windows Update, so you'll need to download and install it yourself. As you'd expect, this update focuses exclusively on security fixes and improvements: Updates the 2020 start date for daylight saving time (DST) in the Kingdom of Morocco. For more information, see KB4557900. Security updates to Windows App Platform and Frameworks, Windows Input and Composition, Windows Media, Windows Kernel, Windows Core Networking, Internet Information Services, Windows Network Security and Containers, Windows Active Directory, the Microsoft JET Database Engine, and Windows Storage and Filesystems. It also has no known issues As for Windows 7, the monthly rollup update is KB4556836 and it can be downloaded manually here. Again, it's only available for businesses that are paying for extended security updates, since support for Windows 7 officially ended back in January. It includes the following changes: Addresses an issue that prevents certain apps from installing if they are published using a Group Policy Object. Addresses an issue that causes Windows to incorrectly report the connection state of a network interface. The issue might cause software that queries the media connection state to receive a result of “Unknown” from a network interface after installing Windows updates released after February 11, 2020. This issue has been observed in the Network Access Manager component of the Cisco AnyConnect Secure Mobility Client. Updates the 2020 start date for daylight saving time (DST) in the Kingdom of Morocco. For more information, see KB4557900. Security updates to Internet Explorer, the Microsoft Scripting Engine, Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Kernel, Internet Information Services, Windows Network Security and Containers, Windows Active Directory, the Microsoft JET Database Engine, and Windows Storage and Filesystems. There aren't any known issues with the update itself, but editions not supported by by Windows 7 ESUs will see an error if they try to install the update: Symptom Workaround After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History. This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the "How to get this update" section of this article. Finally, the Windows 7 security-only update is KB4556843 and it can be downloaded manually here. It includes the following security fixes: Updates the 2020 start date for daylight saving time (DST) in the Kingdom of Morocco. For more information, see KB4557900. Security updates to Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Kernel, Internet Information Services, Windows Network Security and Containers, Windows Active Directory, the Microsoft JET Database Engine, and Windows Storage and Filesystems. The single known issue is the same as what's in the monthly rollup. Source: Patch Tuesday: Here's what's new for Windows 7 and 8.1 this month (Neowin)
  16. Greetings Everyone, I know its too late but still.. This script will help you to create a Microsoft Media Refresh January 2020 disc image (ISO file). Base ISO: Microsoft Media Refresh SP1 November 2010 ISOs (Win7_Pro_SP1_English_x64.iso) This guide assumes that you already have the above mentioned disc image and have made no previous modifications on the ISO. Steps: 1) Manually create four folders viz., Win7, Updates, IE11 & ISO in C:\Drive 2) Mount Disc Image & copy all its Contents to C:\Win7 3) Go to C:\Win7\sources folder & delete ei.cfg file 4) Download KB3020369-x64, kb3125574-v4-x64, KB2729094-v2-x64, KB2670838-x64, KB2834140-v2-x64, KB2639308-x64, KB2990941-v3-x64, KB3087873-v2-x64, kb4474419-v3-x64, kb4490628-x64 & kb4534310-x64 UPDATES from https://catalog.update.microsoft.com/ & paste it to C:\Updates KB2990941 & KB3087873 ain't available on above site. Therefore, download Gigabyte Windows USB Tool and extract it. Link: http://download.gigabyte.eu/FileList/Utility/mb_utility_windowsimagetool.zip Find KB2990941 and KB3087873 from the extracted folder: mb_utility_windowsimagetool\WindowsImageTool\HOTFIX\x64 5) Download IE11 as a Cab File: http://download.microsoft.com/download/7/7/D/77DEA30E-F617-4088-9352-FDBFED2987EE/IE11-Windows6.1-KB2841134-x64.cab & paste it to C:\IE11 6) Download oscdmig and extract it. Link: https://www.sevenforums.com/attachments/tutorials/32382d1256189124-make-bootable-iso-student-d-l-oscdimg.zip Paste it to C:\Windows\System32. For Windows 7 HOMEBASIC Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim PAUSE mkdir C:\HOMEBASIC Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index:1 /MountDir:C:\HOMEBASIC Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3020369-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2729094-v2-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2670838-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2834140-v2-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2639308-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /packagepath:C:\IE11 Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2990941-v3-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3087873-v2-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Dism /Unmount-WIM /MountDir:C:\HOMEBASIC /Commit rmdir C:\HOMEBASIC Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim oscdimg -LTEST -m -u2 -bootdata:2#p0,e,bC:\Win7\boot\etfsboot.com#pEF,e,bC:\Win7\efi\microsoft\boot\efisys.bin C:\Win7\ C:\ISO\Win7UEFI.ISO PAUSE For Windows 7 HOMEPREMIUM Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim PAUSE mkdir C:\HOMEPREMIUM Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index:2 /MountDir:C:\HOMEPREMIUM Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3020369-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2729094-v2-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2670838-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2834140-v2-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2639308-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /packagepath:C:\IE11 Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2990941-v3-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3087873-v2-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Dism /Unmount-WIM /MountDir:C:\HOMEPREMIUM /Commit rmdir C:\HOMEPREMIUM Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim oscdimg -LTEST -m -u2 -bootdata:2#p0,e,bC:\Win7\boot\etfsboot.com#pEF,e,bC:\Win7\efi\microsoft\boot\efisys.bin C:\Win7\ C:\ISO\Win7UEFI.ISO PAUSE For Windows 7 PROFESSIONAL Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim PAUSE mkdir C:\PROFESSIONAL Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index:3 /MountDir:C:\PROFESSIONAL Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3020369-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2729094-v2-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2670838-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2834140-v2-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2639308-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /packagepath:C:\IE11 Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2990941-v3-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3087873-v2-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Dism /Unmount-WIM /MountDir:C:\PROFESSIONAL /Commit rmdir C:\PROFESSIONAL Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim oscdimg -LTEST -m -u2 -bootdata:2#p0,e,bC:\Win7\boot\etfsboot.com#pEF,e,bC:\Win7\efi\microsoft\boot\efisys.bin C:\Win7\ C:\ISO\Win7UEFI.ISO PAUSE For Windows 7 ULTIMATE Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim PAUSE mkdir C:\ULTIMATE Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index:4 /MountDir:C:\ULTIMATE Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3020369-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2729094-v2-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2670838-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2834140-v2-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2639308-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /packagepath:C:\IE11 Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2990941-v3-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-KB3087873-v2-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Dism /Unmount-WIM /MountDir:C:\ULTIMATE /Commit rmdir C:\ULTIMATE Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim oscdimg -LTEST -m -u2 -bootdata:2#p0,e,bC:\Win7\boot\etfsboot.com#pEF,e,bC:\Win7\efi\microsoft\boot\efisys.bin C:\Win7\ C:\ISO\Win7UEFI.ISO PAUSE For Windows 7 AIO Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim PAUSE mkdir C:\HOMEBASIC Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index:1 /MountDir:C:\HOMEBASIC Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3020369-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2729094-v2-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2670838-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2834140-v2-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2639308-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /packagepath:C:\IE11 Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2990941-v3-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3087873-v2-x64.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Dism /Image:C:\HOMEBASIC /Add-Package /PackagePath:C:\Updates\windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Dism /Unmount-WIM /MountDir:C:\HOMEBASIC /Commit rmdir C:\HOMEBASIC mkdir C:\HOMEPREMIUM Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index:2 /MountDir:C:\HOMEPREMIUM Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3020369-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2729094-v2-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2670838-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2834140-v2-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2639308-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /packagepath:C:\IE11 Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2990941-v3-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3087873-v2-x64.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Dism /Image:C:\HOMEPREMIUM /Add-Package /PackagePath:C:\Updates\windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Dism /Unmount-WIM /MountDir:C:\HOMEPREMIUM /Commit rmdir C:\HOMEPREMIUM mkdir C:\PROFESSIONAL Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index:3 /MountDir:C:\PROFESSIONAL Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3020369-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2729094-v2-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2670838-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2834140-v2-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2639308-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /packagepath:C:\IE11 Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2990941-v3-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3087873-v2-x64.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Dism /Image:C:\PROFESSIONAL /Add-Package /PackagePath:C:\Updates\windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Dism /Unmount-WIM /MountDir:C:\PROFESSIONAL /Commit rmdir C:\PROFESSIONAL mkdir C:\ULTIMATE Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index:4 /MountDir:C:\ULTIMATE Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB3020369-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2729094-v2-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2670838-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2834140-v2-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2639308-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /packagepath:C:\IE11 Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\Windows6.1-KB2990941-v3-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-KB3087873-v2-x64.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates\windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Dism /Unmount-WIM /MountDir:C:\ULTIMATE /Commit rmdir C:\ULTIMATE Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim oscdimg -LTEST -m -u2 -bootdata:2#p0,e,bC:\Win7\boot\etfsboot.com#pEF,e,bC:\Win7\efi\microsoft\boot\efisys.bin C:\Win7\ C:\ISO\Win7UEFI.ISO PAUSE Copy the script of your choice & paste it to notepad. Ensure the script is saved as a batch file (ending in extension .bat). Note: This script must be run uninterrupted and it takes at least a couple of hours to run so you will want to prevent your computer from going to sleep or for interference from the likes of Windows Update during this time. I myself tested the Windows 7 AIO Script & it took around 5 hours on my 6th generation intel skylake system. Here is the command line interface of Win 7 AIO Script(Extract): C:\Windows\system32>Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Details for image : C:\Win7\sources\install.wim Index : 1 Name : Windows 7 HOMEBASIC Description : Windows 7 HOMEBASIC Size : 11,710,161,360 bytes Index : 2 Name : Windows 7 HOMEPREMIUM Description : Windows 7 HOMEPREMIUM Size : 12,222,587,449 bytes Index : 3 Name : Windows 7 PROFESSIONAL Description : Windows 7 PROFESSIONAL Size : 12,122,886,417 bytes Index : 4 Name : Windows 7 ULTIMATE Description : Windows 7 ULTIMATE Size : 12,285,492,779 bytes The operation completed successfully. C:\Windows\system32>PAUSE Press any key to continue . . . C:\Windows\system32>mkdir C:\ULTIMATE C:\Windows\system32>Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index: 4 /MountDir:C:\ULTIMATE Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Mounting image [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \Windows6.1-KB3020369-x64.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Processing 1 of 1 - Adding package C:\Updates\Windows6.1-KB3020369-x64.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Processing 1 of 1 - Adding package C:\Updates\windows6.1-kb3125574-v4-x64_2dafb1 d203c8964239af3048b5dd4b1264cd93b9.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \Windows6.1-KB2729094-v2-x64.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\Windows6.1-KB2729094-v2-x64.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \Windows6.1-KB2670838-x64.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\Windows6.1-KB2670838-x64.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \Windows6.1-KB2834140-v2-x64.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\Windows6.1-KB2834140-v2-x64.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \Windows6.1-KB2639308-x64.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\Windows6.1-KB2639308-x64.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /packagepath:C:\IE11 Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package Microsoft-Windows-InternetExplorer-Package-To pLevel~31bf3856ad364e35~amd64~~11.2.9600.16428 [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \Windows6.1-KB2990941-v3-x64.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\Windows6.1-KB2990941-v3-x64.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \windows6.1-KB3087873-v2-x64.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\windows6.1-KB3087873-v2-x64.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\windows6.1-kb4474419-v3-x64_b5614c 6cea5cb4e198717789633dca16308ef79c.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\windows6.1-kb4490628-x64_d3de52d69 87f7c8bdc2c015dca69eac96047c76e.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Package /PackagePath:C:\Updates \windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package C:\Updates\windows6.1-kb4534310-x64_4dc78a6ee b14e2eac1ede7381f4a93658c8e2cdc.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Unmount-WIM /MountDir:C:\ULTIMATE /Commit Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image File : C:\Win7\sources\install.wim Image Index : 4 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>rmdir C:\ULTIMATE C:\Windows\system32>Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Details for image : C:\Win7\sources\install.wim Index : 1 Name : Windows 7 HOMEBASIC Description : Windows 7 HOMEBASIC Size : 14,867,750,897 bytes Index : 2 Name : Windows 7 HOMEPREMIUM Description : Windows 7 HOMEPREMIUM Size : 15,386,654,205 bytes Index : 3 Name : Windows 7 PROFESSIONAL Description : Windows 7 PROFESSIONAL Size : 15,291,878,047 bytes Index : 4 Name : Windows 7 ULTIMATE Description : Windows 7 ULTIMATE Size : 15,454,575,521 bytes The operation completed successfully. C:\Windows\system32>oscdimg -LTEST -m -u2 -bootdata:2#p0,e,bC:\Win7\boot\etfsboo t.com#pEF,e,bC:\Win7\efi\microsoft\boot\efisys.bin C:\Win7\ C:\ISO\Win7UEFI.ISO OSCDIMG 2.54 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2007. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (500 files in 46 directories) Scanning source tree complete (876 files in 200 directories) Computing directory information complete Image file is 5166202880 bytes Writing 876 files in 200 directories to C:\ISO\Win7UEFI.ISO 100% complete Final image file is 5168396288 bytes Done. C:\Windows\system32>PAUSE Press any key to continue . . . Host System: Windows 7 x64 CREDITS: @philipyip
  17. Greetings everyone, This guide is in continuation of my previous topic. It will help you to integrate latest Microsoft .NET Framework 4.8(Recommended) & Visual C++ Redistributable Packages install runtime components(Optional) in Win7UEFI.iso which was previously created in C:\ISO folder. This is the last thing you should do after slipstreaming all necessary updates & drivers(if any) in Windows 7 Disc Image (ISO file). STEPS: 1) Manually create WinTemp & WA2Manual folder in C:\ Drive. 2) Mount the above ISO & copy all its contents to C:\WinTemp. 3) Download simple conversion/manual integration pack for addons & extract it to C:\WA2Manual. Link: https://m.put.re/99TkTpX2.zip 4) Download dotNetFx48_20200114_x64.WA & vcredist_x64_Win7_20191015.WA from below link and copy it to C:\WA2Manual. https://github.com/abbodi1406/dotNetFx4xW7A/releases/tag/20.01.14 https://gitlab.com/stdout12/adns/uploads/21564cca02c77c5571511a5acd54e5a7/vcredist_x64_Win7_20191015.WA 5) Run WA2MAN.cmd & wait for its completion. It will create two sub-folder viz., dotNetFx48_20200114_x64 & vcredist_x64_Win7_20191015 6) Now mount the index(s): For Windows 7 HOMEBASIC For Windows 7 HOMEPREMIUM For Windows 7 PROFESSIONAL For Windows 7 ULTIMATE For Windows 7 AIO Save it as a batch file on desktop say "mount.bat" and then right click on it & run as admin. 7) Now integrate the dotnet & VCredist by running Integrator.cmd as admin created on above sub-folder. Enter the mounted path say C:\PROFESSIONAL. For Win7AIO you have to run Integrator.cmd 4 TIMES to cover all indexes. In Total 8(=4+4)Times. Finally unmount the index(s): For Windows 7 HOMEBASIC For Windows 7 HOMEPREMIUM For Windows 7 PROFESSIONAL For Windows 7 ULTIMATE For Windows 7 AIO Save it as a batch file say "unmount.bat" on Desktop & run as admin New Disc Image(ISO file) will be created in C:\ Drive. Credits: @abbodi1406
  18. This new Zoom security flaw lets hackers target Windows 7 PCs Windows 7 devices at risk from Zoom Zero Day vulnerability (Image credit: Shutterstock) Zoom is facing more security scrutiny after a new flaw was found to open up the service to hackers, putting Windows 7 users at risk. Researchers at Slovenian cybersecurity firm ACROS Security has revealed a previously unknown flaw in the videoconferencing software Zoom could allow a hacker to remotely commandeer computers running old versions of the Microsoft Windows operating system. The “zero-day” vulnerability applies to Zoom software running on Windows 7, or even older operating systems. Windows 7 Zoom ACROS Security noted that anyone able to successfully exploit the vulnerability could access files on the vulnerable computer, and even take over the entire device. Microsoft has been trying to convince Windows 7 users to upgrade to newer software versions in recent years, but with little success - despite offering free upgrades to Windows 10. The company revealed it would be ending technical support out for Windows 7 on January 15 2020, meaning it would no longer offer patches and security updates for Windows 7. That means that any bugs or problems still found in the software will never get fixed. Likewise, any security vulnerabilities could also remain in Windows 7, as Microsoft is unlikely to patch those unless they are very severe – more on that in a moment. Many large organisations, including the NHS, still use Windows 7 on many devices, with Microsoft allowing customers to pay extra to receive specilaised support. “Zoom takes all reports of potential security vulnerabilities seriously,” a Zoom spokesperson said in a statement. “This morning we received a report of an issue impacting users running Windows 7 and older. We have confirmed this issue and are currently working on a patch to quickly resolve it.” The issue is the latest in a litany of security worries for Zoom, which has exploded in popularity in 2020 thanks to the remote working boom caused by the global pandemic. The sudden and increased demand on the company's systems was unlike anything most companies have ever experienced, with criminals also attacking Zoom with gusto. Following a number of high-profile issues, company's CEO Eric S. Yuan promised more transparency and announce a 90-day freeze on all new features not related to privacy, safety or security back in April - however this deadline was missed earlier this month. This new Zoom security flaw lets hackers target Windows 7 PCs
  19. 0Patch publishes micropatch to address Windows Font Parsing vulnerability Microsoft published an advisory about a new font parsing vulnerability in Windows on March 23, 2020. The company rated the vulnerability as critical and said that it was aware of limited targeted attacks exploiting the vulnerability. Microsoft listed several workarounds to mitigate attacks but they all reduced functionality for users in one way or another. Microsoft has yet to release a security patch to address the issue for all versions of Windows affected by the vulnerability. Security company 0Patch, well-known for its pledge to create and distribute patches for the Windows 7 and Windows Server 2008 R2 operating systems that ran out of official support this year. While business and Enterprise customers may extend support by up to three years, home users cannot officially and 0Patch patches. Microsoft already announced that it won't provide the font parsing patch for unsupported versions of Windows 7 while it will provide it to companies and Enterprise organizations that have joined the ESU program to receive extended support updates. 0Patch announced today that it has created a micro-patch for the font parsing vulnerability that affects all major client and server versions of the Windows operating system. A blog post on the official 0Patch blog lists the official information and analyzes the workarounds that Microsoft posted. While all work to a degree, all have disadvantages that 0Patch highlights. Disabling the preview pane, details pane and thumbnails in Windows Explorer for example only blocks attacks when the file manager is used but it won't protect against other attack vectors. The team analyzed the vulnerability -- it had to since Microsoft did not disclose details about it -- and found a solution that it turned into a micro patch. Basically, what 0Patch did was put a bouncer in front of font operations if Adobe Type 1 Script fonts are used so that the vulnerability cannot be exploited. So we decided to find the common execution point that various Windows applications such as Windows Explorer, Font Viewer, and applications using Windows-integrated font support are using to pass a font to Windows, then place a bouncer there that would keep Adobe Type 1 PostScript fonts out. The blog post goes into detail and users interested in additional details may check it out for additional information on the implementation. All administrators need to do is install the micro patch on the device to protect it against the vulnerability. With this micropatch in place, all applications using Windows GDI for font-related operations will find any Adobe Type 1 PostScript fonts rendered invalid and unable to load. For example, Windows Explorer will start looking like this when viewing a folder with a pair of otherwise valid PFM and PFB files. The patch is available for free for Windows 7 64-bit and Windows Server 2008 R2 without Extended Security Updates. 0Patch plans to create patches for ESU versions of Windows 7 and Windows Server 2008 R2, as well as Windows 8.1 and Windows Server 2012 soon as well. Windows 10 and Server won't receive the patch as these systems face less of a risk from the vulnerability than previous versions of Windows. Here is a video by the company: Source: 0Patch publishes micropatch to address Windows Font Parsing vulnerability (gHacks - Martin Brinkmann)
  20. Key Points The Windows 7 upgrade cycle is not as far along as it usually is this far along, Microsoft finance chief Amy Hood said on Monday. Around 23% of Windows desktop machines are still running Windows 7. Microsoft still sees plenty of opportunity to for customers to upgrade machines from Windows 7 to Windows 10, and not only because of coronavirus fallout. Usually, Microsoft sees a pronounced increase in revenue around the time it ends support for an older version of its Windows operating system as individuals and companies buy PCs with the latest from Microsoft. Then, over time, the impact tails off, making for tougher year-over-year upgrade comparisons. It's taking longer this time around, which could spread out the revenue generated from the upgrade process to additional quarters. Analysts watch Windows revenue closely, as it gives Microsoft 15% of its revenue and meaningful profit. Amy Hood, Microsoft's finance chief, indicated to analysts in January that China's public health situation and a chip shortage could be factors in the prolonged Windows refresh cycle. At the time, she issued a quarterly revenue guidance range for the business segment including Windows that was wider than usual to reflect impact from the coronavirus in particular. Then, last week, in the midst of a market selloff, Microsoft said it did not expect to reach that guidance range, sending Microsoft and other stocks lower. The cycle is not as far along as it usually is at this point in the timeline, Hood said on Monday during a conversation with Morgan Stanley analyst Keith Weiss at Morgan Stanley's Technology Media and Telecom conference in San Francisco. Microsoft ended support for Windows 7 in January. Here's what Hood said: I think, in general, these cycles tend to look similar. But what I would say is this one is certainly more complicated by a number of things that I'll talk about in a second. What is different about this is there still remains quite a bit of opportunity more than we saw at this point in the prior cycle. A lot of that exists where you would expect it to exist, which is small and medium business segment. Not unusual, but it means that we do have some room to continue to grow and likely means that the curve will look different than last time in terms of its shape. Now, then you add to it two complicating factors, one of which you brought up, which have been chip supply, which has impacted some of the growth rates over the past bit. And then, the second one which is the supply chain currently in China in terms of bindings and productions. And so those will — and as we've talked about, will impact the quarterly results. And so I'm not sure it'll look like the exact same curve in terms of the prior cycle, not just because we have a little bit more left to go than we have had in prior cycles, but also because it's been a bit more volatile due to those two issues as we work through them. Microsoft released Windows 7 in 2009. Other than Windows 10, it's the most popular version of Windows on desktop, with about 23% share in February, according to Statcounter. Windows 8 and Windows 8.1, which came out in 2012 and 2013, respectively, are less widely used than Windows 7. Microsoft said in 2018 that there were 1.5 billion Windows devices. "I feel great that we're executing well on end of support," Hood said on Monday, speaking of older versions of Windows PC licenses and other products. "It builds a great funnel for us as we think about transition to the cloud for customers and helping them on their hybrid journey." Source
  21. Microsoft to support new Edge browser until July 15, 2021 on Windows 7 Microsoft released the first stable version of the company's new Chromium-based Microsoft Edge web browser one day after it ended support for its Windows 7 operating system. Support for Windows 7 ended on January 14, 2020 for Home customers. Business and Enterprise customers have options to extend support by up to three years if they pay Microsoft for Extended Security Updates. The release of the new Microsoft Edge web browser for Windows 7 raised some questions. One of the main questions concerned support for the browser under Windows 7. For how long would Microsoft support the Chromium-based Edge browser on Windows 7? Microsoft has now provided an answer to that question. According to the company, the new Microsoft Edge web browser will be supported on Windows 7 and Windows Server 2008 R2 until July 15, 2021. We will continue to support Microsoft Edge on Windows 7 and Windows Server 2008 R2 until July 15, 2021. These operating systems are out of support and Microsoft recommends you move to a supported operating system such as Windows 10. While Microsoft Edge helps keep you more secure on the web, your PC may still be vulnerable to security risks. In order for IE mode to be supported on these operating systems the devices will need to have the Extended Security Updates for Windows 7. Without the Windows 7 Extended Security updates Internet Explorer functionality will be vulnerable to security risks. Additionally, IE mode functionality may cease to work without the continued servicing through the extended security updates. The browser's IE Mode (Internet Explorer mode) is only available on systems that have joined the Extended Security Updates program because of security risks involved. One question that has not been answered in the context is whether the new Microsoft Edge browser will remain supported for customers with Extended Security Updates functionality beyond July 15, 2021. These may get support until early 2023 for Windows 7 and Windows Server 2008 R2, and ending Edge support early may not sit well with some of these customers. Source: Microsoft to support new Edge browser until July 15, 2021 on Windows 7 (gHacks - Martin Brinkmann)
  22. Greetings everyone, This guide will help you to manually backup all third-party drivers (non- microsoft drivers) from an existing Windows 7 installation. I did some testing and found that all the hardware drivers are stored in C:\Windows\System32\DriverStore\FileRepository directory. What you have to do is: (i)Go to C:\Windows\System32\DriverStore\FileRepository (ii)Sort by last modified date & (iii)Check and copy folder for non-microsoft drivers to say C:\Drivers. That's all IGNORE those folder which don't contain *.cat file. I also slipstreamed the above drivers in Windows 7 January 2020 Disc Image & it integrated successfully. Command Line Interface(Extract): C:\Windows\system32>Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim Deployment Image Servicing and Management tool Version: 6.1.7601.24499 Details for image : C:\Win7\sources\install.wim Index : 1 Name : Windows 7 HOMEBASIC Description : Windows 7 HOMEBASIC Size : 14,867,750,897 bytes Index : 2 Name : Windows 7 HOMEPREMIUM Description : Windows 7 HOMEPREMIUM Size : 15,386,654,205 bytes Index : 3 Name : Windows 7 PROFESSIONAL Description : Windows 7 PROFESSIONAL Size : 15,291,878,047 bytes Index : 4 Name : Windows 7 ULTIMATE Description : Windows 7 ULTIMATE Size : 15,454,575,521 bytes The operation completed successfully. C:\Windows\system32>PAUSE Press any key to continue . . . C:\Windows\system32>mkdir C:\ULTIMATE C:\Windows\system32>Dism /Mount-WIM /WimFile:C:\Win7\sources\install.wim /index: 4 /MountDir:C:\ULTIMATE Deployment Image Servicing and Management tool Version: 6.1.7601.24499 Mounting image [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism /Image:C:\ULTIMATE /Add-Driver /Driver:C:\Drivers /Recu rse Deployment Image Servicing and Management tool Version: 6.1.7601.24499 Image Version: 6.1.7601.24499 Searching for driver packages to install... Found 19 driver package(s) to install. Installing 1 of 19 - C:\Drivers\atheros_bth.inf_amd64_neutral_7f7d27b8abb6001a\a theros_bth.inf: The driver package was successfully installed. Installing 2 of 19 - C:\Drivers\dptf_cpu.inf_amd64_neutral_aa6e0c437ab150d5\dptf _cpu.inf: The driver package was successfully installed. Installing 3 of 19 - C:\Drivers\esif_manager.inf_amd64_neutral_c73fefaf22ba926a\ esif_manager.inf: The driver package was successfully installed. Installing 4 of 19 - C:\Drivers\hdxma7.inf_amd64_neutral_9bbcdf3b5e3fc734\hdxma7 .inf: The driver package was successfully installed. Installing 5 of 19 - C:\Drivers\heci.inf_amd64_neutral_16593ab35133f7a6\heci.inf : The driver package was successfully installed. Installing 6 of 19 - C:\Drivers\iaahcic.inf_amd64_neutral_0a9d931ff5b9c7cf\iaAHC IC.inf: The driver package was successfully installed. Installing 7 of 19 - C:\Drivers\ialpss2_gpio2_skl.inf_amd64_neutral_be53f7a7c63d ac92\iaLPSS2_GPIO2_SKL.inf: The driver package was successfully installed. Installing 8 of 19 - C:\Drivers\ialpss2_i2c_skl.inf_amd64_neutral_b2e38689a4eb38 7b\iaLPSS2_I2C_SKL.inf: The driver package was successfully installed. Installing 9 of 19 - C:\Drivers\intcdaud.inf_amd64_neutral_66e0a5048e30f9c5\Intc DAud.inf: The driver package was successfully installed. Installing 10 of 19 - C:\Drivers\k120130.inf_amd64_neutral_299d0c74ec099c32\K120 130.inf: The driver package was successfully installed. Installing 11 of 19 - C:\Drivers\netathr7x.inf_amd64_neutral_f6b1b7669e6ad5b3\ne tathr7x.inf: The driver package was successfully installed. Installing 12 of 19 - C:\Drivers\rt64win7.inf_amd64_neutral_ded7d70457da510f\rt6 4win7.inf: The driver package was successfully installed. Installing 13 of 19 - C:\Drivers\rtsuerx.inf_amd64_neutral_c49dd1b16298e63c\RtsU erX.inf: The driver package was successfully installed. Installing 14 of 19 - C:\Drivers\sunrisepoint-lpsystem.inf_amd64_neutral_c08c10f a27075155\sunrisepoint-lpsystem.inf: The driver package was successfully install ed. Installing 15 of 19 - C:\Drivers\sunrisepoint-lpsystemlpss.inf_amd64_neutral_244 c81f76a71145b\sunrisepoint-lpsystemlpss.inf: The driver package was successfully installed. Installing 16 of 19 - C:\Drivers\sunrisepoint-lpsystemthermal.inf_amd64_neutral_ 7e014774b9c5f768\sunrisepoint-lpsystemthermal.inf: The driver package was succes sfully installed. Installing 17 of 19 - C:\Drivers\synpd.inf_amd64_neutral_5ab01e2e519fd6f2\synpd. inf: The driver package was successfully installed. Installing 18 of 19 - C:\Drivers\USB\iusb3hub.inf: The driver package was succes sfully installed. Installing 19 of 19 - C:\Drivers\USB\iusb3xhc.inf: The driver package was succes sfully installed. The operation completed successfully. C:\Windows\system32>Dism /Unmount-WIM /MountDir:C:\ULTIMATE /Commit Deployment Image Servicing and Management tool Version: 6.1.7601.24499 Image File : C:\Win7\sources\install.wim Image Index : 4 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>rmdir C:\ULTIMATE C:\Windows\system32>Dism /Get-WimInfo /WimFile:C:\Win7\sources\install.wim Deployment Image Servicing and Management tool Version: 6.1.7601.24499 Details for image : C:\Win7\sources\install.wim Index : 1 Name : Windows 7 HOMEBASIC Description : Windows 7 HOMEBASIC Size : 16,074,956,469 bytes Index : 2 Name : Windows 7 HOMEPREMIUM Description : Windows 7 HOMEPREMIUM Size : 16,593,602,612 bytes Index : 3 Name : Windows 7 PROFESSIONAL Description : Windows 7 PROFESSIONAL Size : 16,498,828,957 bytes Index : 4 Name : Windows 7 ULTIMATE Description : Windows 7 ULTIMATE Size : 16,661,516,327 bytes The operation completed successfully. C:\Windows\system32>PAUSE Press any key to continue . . . Regards. EDIT 1 : As an extra precaution(optional), it's better to delete the *.pnf files from copied folders as these files are machine-specific and are created by the system when the driver is installed for device. EDIT 2: If you're planning to slipstreamed all third-party drivers like I do above then don't forget to integrate dotNet also in Windows 7 January 2020 ISOs as some drivers malfunction like MaxxAudioPro, Synaptics Touchpad Driver, etc. without it. EDIT 3: Or you can simply use this third-party program called Windows Download Integrator (Not Recommended) shared by @Mach1 to do this work for you. CREDITS: @abbodi1406
  23. vizit

    Driver update

    I am looking for a free software to update the drivers. A lot of software are available over the internet but all are not up to the mark. They are lagging one way or the other. So I request you to please suggest me a good software to update the drivers
  24. It appears that the Windows 7 ESU Bypass is indeed working Support for Microsoft's Windows 7 operating system ended on January 14, 2020 officially. Home users cannot extend support for the operating system while business and Enterprise customers may extend support by up to three years; this is done by joining the ESU program which is available per machine (business) or per user (Enterprise). A bypass to use ESU-only patches on Home machines -- basically any machine that has not joined the program officially -- was discovered and published in December 2019. The bypass worked with the test ESU patch that Microsoft released but it was not clear back then if it would also work with "real" patches. Now that the first post-Windows 7 support patch has been released, confirmations are coming in that the bypass is indeed working. Note: we suggest that backups are created of important data, better the entire system, before the bypass or any of the updates that Microsoft released for Windows 7 are installed. If something goes wrong, it is then possible to go back to the previous version without losing any data. The process of using the bypass with the Windows 7 patches released in February would look like this (note that you should not install the latest SSU KB4537829 as the bypass does not seem to work anymore if it is installed). Install the bypass. You can grab the latest version from the MDL forum (account needed), or download it from Gitlab. The password is 2020. Download and install the ESU Test update KB4528069. It should install fine. Restart the System. Install the following updates: KB4538483, KB4537820, KB4537767, and KB4537813. Restart the system. Our colleagues over at Deskmodder found another option that supports the installation of the latest SSU: Install the bypass. Install the ESU Test update. Remove the bypass. Install the SSU KB4537829. Install the KB4537820 update. Closing Words It remains to be seen if the bypass will continue to work in the coming months or years.For now, it may be an option in some situations provided that backups are created. Source: It appears that the Windows 7 ESU Bypass is indeed working (gHacks - Martin Brinkmann)
  25. Here's what's new for Windows 8.1 and 7 this Patch Tuesday We're already three months deep into 2021, and as we reach the second Tuesday of March, that means it's time once again for Microsoft to update every supported version of Windows. Naturally, the most recent versions of Windows 10 are getting updates, but Windows 8.1 is also still supported. And, for businesses paying for extended security updates, so is Windows 7. There are updates heading out to both of these Windows releases, and as usual, there are two types of updates for both Windows 8.1 and Windows 7, as well as their server counterparts - a monthly rollup that's usually installed automatically and a security-only update that you have to install manually. Starting with Windows 8.1, the monthly rollup update is labeled KB5000848 and you can download it manually here. It includes the following changes: Addresses an issue in which a non-native device that is in the same realm does not receive a Kerberos Service ticket from Active Directory DCs. This issue occurs even though Windows Updates are installed that contain CVE-2020-17049 protections released between November 10 and December 8, 2020 and configured PerfromTicketSignature to 1 or larger. Ticket acquisition fails with KRB_GENERIC_ERROR if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without the USER_NO_AUTH_DATA_REQUIRED flag being set for the user in User Account Controls. Addresses an elevation of privilege security vulnerability documented in CVE-2021-1640 related to print jobs submitted to “FILE:” ports. After installing Windows updates from March 9, 2021 and later, print jobs that are in a pending state before restarting the print spooler service or restarting the OS will remain in an error state. Manually delete the affected print jobs and resubmit them to the print queue when the print spooler service is online. Security updates to Windows Fundamentals, Windows Shell, Windows UAC, Windows Hybrid Cloud Networking, Windows Media, and Windows Graphics. There's a single known issue, which is the same we've been seeing for months now: Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release. And as for the security-only update, that's KB5000853, and you can download it manually here. It includes the first and last bullet points from the monthly rollup update, and it has the same known issue. Moving on to Windows 7, again, you'll need to be paying for extended security updates to get any updates at this point. If you are, the monthly rollup you'll get is KB5000841 and you can download it manually here. Here's what's included: Addresses an elevation of privilege security vulnerability documented in CVE-2021-1640 related to print jobs submitted to “FILE:” ports. After installing Windows updates from March 9, 2021 and later, print jobs that are in a pending state before restarting the print spooler service or restarting the OS will remain in an error state. Manually delete the affected print jobs and resubmit them to the print queue when the print spooler service is online. Addresses an issue in which a non-native device that is in the same realm does not receive a Kerberos Service ticket from Active Directory DCs. This issue occurs even though Windows Updates are installed that contain CVE-2020-17049 protections released between November 10 and December 8, 2020 and configured PerfromTicketSignature to 1 or larger. Ticket acquisition fails with KRB_GENERIC_ERROR if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without the USER_NO_AUTH_DATA_REQUIRED flag being set for the user in User Account Controls. Security updates to Windows Fundamentals, Windows Shell, Windows UAC, Windows Hybrid Cloud Networking, and Windows Media. The single known issue is the same as the one for the Windows 8.1 updates. Finally, the security-only update for Windows 7 is KB5000851 and it can be downloaded manually here. It only includes the last two points of the updates mentioned above and has the same known issue as the other updates. Source: Here's what's new for Windows 8.1 and 7 this Patch Tuesday
×
×
  • Create New...