Phàm đã dùng 1 sản phẩm phần mềm,bất kỳ ai cũng muốn được cập nhất các bản vá mới nhất. Với người dùng Windows cũng vậy,những hotfix luôn giúp hệ thống của bạn được bảo mật và chạy trơn tru hơn . Nhưng vì 1 lý do nào đó như dùng bản Windows lậu,muốn thiết lập Windows cập nhật khi bạn rảnh rỗi [ vì quá trình
cập nhật mất khá nhiều thời gian ]...... Vì thế bài viết này sẽ Hướng dẫn bật hoặc tắt tính năng Windows Update trong mọi hệ điều hành của Microsoft như Windows 7,Windows 8.1,Windows 10,Windows Server ...... Như mọi bài viết của www.KeyPhanMem.info sẽ đưa ra nhiều cách để người dùng chọn lựa . Cách 1 : Sử dụng tính năng Services trong Windows.
Đầu tiên bạn chạy Windows Command với quyền Administrator ,gõ lệnh :
services.msc và Enter.
Tiếp đó bạn đợi 1 chút để truy cập vào tính năng Services trong hệ điều hành Windows .
Bạn tìm tới mục Windows Update,nháy chuột phải vào đây và chọn Properties như hình.
Tới đây ở mục Startup type : Bạn có thể cấu hình tắt Windows Update [ Disabled ],để chế độ tự động [ Automatic ]hay chế độ thủ công Manual....
Cách 2 : Sử dụng Local Group Policy
Tương tự như cách 1,nhưng trong Windows Command bạn gõ lệnh gpedit.msc để truy cập vào tính năng Local Group Policy Editor và truy cập vào nhánh sau :
User Configuration\Administrative Templates\Windows Components\Windows Update
Bạn nháy chuột phải vào mục : Remove
access to use all Windows Update features và chọn Edit.
Để bật tính năng truy cập Windows Update ta chọn Not Configured hoặc Disabled và ngược lại.
Ngoài ra ở mục Configure Notifications ta cũng có thể thiết lập Show restart required notifications - hiển thị thông báo yêu cầu khởi động lại máy hoặc không hiển thị bất kỳ thông báo nào với tùy chọn : Do not show any notifications
Tiếp đó ta Log Off hoặc khởi động lại máy để thay đổi
này có hiệu lực.
Cách 3 : Sử dụng File Registry được biên soạn sẵn .
Bạn chỉ cần vào đây để tải về các file registry,ở đó www.KeyPhanMem.info đã soạn sẵn với các tùy chỉnh.
Như vậy là chúng tôi đã giới thiệu 3 cách tới bạn đọc. Nếu có giải pháp nào hữu ích thêm. Mời bạn đóng góp nhé.
Cám ơn các bạn đã đọc bài viết này. Chúc các bạn thành công và hi vọng những bài viết từ www.KeyPhanMem.info sẽ mang lại thú vị và trải nghiệm thêm tới bạn. Mọi thắc mắc,góp ý với chúng tôi .Các bạn có thể để lại comment ở cuối bài. Chúng tôi luôn lắng nghe và sẻ chia dưới góc độ cầu thị nhất ! Trân trọng !
Hướng dẫn bật hoặc tắt tính năng Windows Update
Skip to main content
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
- Article
- 03/24/2022
- 6 minutes to read
In this article
Applies to: Windows 10, version 1809 and later versions, Windows 8.1,
Windows Server 2012 R2, Windows 7, Windows Server 2008 R2
Original KB number: 947821
Symptom
Windows updates and service packs may fail to install if there are corruption errors. For example, an update might not install if a system file is damaged. The DISM or System Update Readiness tool may help you to fix some Windows corruption errors.
This article is intended for Support agents and IT professionals. If you are home users and looking for more information about fixing Windows update errors, see Fix Windows Update errors.
Resolution for Windows 8.1, Windows 10 and Windows Server 2012 R2
To resolve this problem, use the inbox Deployment Image Servicing and Management [DISM] tool. Then, install the Windows update or service pack again.
Open an elevated command prompt. To do this, open Start menu or Start screen, type Command Prompt, right-select Command Prompt, and then select Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or select Allow.
Type the following command, and then press Enter. It may take several minutes for the command operation to be completed.
DISM.exe /Online /Cleanup-image /Restorehealth
Important
When you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions. However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
Note
Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, reference Repair a Windows Image.
Type the
sfc /scannow
command and press Enter. It may take several minutes for the command operation to be completed.Close the command prompt, and then run Windows Update again.
DISM creates a log file [%windir%/Logs/CBS/CBS.log] that captures any issues that the tool found or fixed. %windir% is the folder in which Windows is installed. For example, the %windir% folder is C:\Windows.
Resolution for Windows 7 and Windows Server 2008 R2
To resolve this problem, use the System Update Readiness tool. Then, install the Windows update or service pack again.
Download the System Update Readiness tool.
Go to Microsoft Update Catalog and download the tool that corresponds to the version of Windows that is running on your computer. For more information about how to find the version of Windows that you installed, see Find out if your computer is running the 32-bit or 64-bit version of Windows.
Note
This tool is updated regularly, we recommend that you always download the latest version. This tool is not available in every supported language. Check the link below to see if it is available in your language.
Install and run the tool.
Select Download on the Download Center webpage, then do one of the following:
- To install the tool immediately, select Open or Run, and then follow the instructions on your screen.
- To install the tool later, select Save, and then download the installation file to your computer. When you're ready to install the tool, double-select the file.
In the Windows Update Standalone Installer dialog box, select Yes.
When the tool is being installed, it automatically runs. Although it typically takes less than 15 minutes to run, it might take much longer on some computers. Even if the progress bar seems to stop, the scan is still running, so don't select Cancel.
When you see Installation complete, select Close.
Reinstall the update or service pack you were trying to install previously.
To manually fix corruption errors that the tool detects but can't be fixed, see How to fix errors that are found in the CheckSUR log file.
Resolution - Download the package from Microsoft Update Catalog directly
You can also try to directly download the update package from Microsoft Update Catalog, and then install the update package manually.
For example, you may have problems when you try to install updates from Windows Update. In this situation, you can download the update package and try to install the update manually. To do this, follow these steps:
Open Microsoft Update Catalog page for KB3006137.
Find the update that applies to your operating system appropriately in the search results, and then select the Download button.
Select the link of the file to download the update.
Select Close after the download process is done. Then, you can find a folder that contains the update package in the location that you specified.
Open the folder, and then double-select the update package to install the update.
If the Windows update or service pack installed successfully, you are finished. If the problem is not fixed, or if System Update Readiness Tool cannot find the cause, contact us for more help.
Description of the common corruption errors
The following table lists the possible error code with Windows Update for your reference:
0x80070002 | ERROR_FILE_NOT_FOUND | The system cannot find the file specified. |
0x8007000D | ERROR_INVALID_DATA | The data is invalid. |
0x800F081F | CBS_E_SOURCE_MISSING | The source for the package or file not found. |
0x80073712 | ERROR_SXS_COMPONENT_STORE_CORRUPT | The component store is in an inconsistent state. |
0x800736CC | ERROR_SXS_FILE_HASH_MISMATCH | A component's file does not match the verification information present in the component manifest. |
0x800705B9 | ERROR_XML_PARSE_ERROR | Unable to parse the requested XML data. |
0x80070246 | ERROR_ILLEGAL_CHARACTER | An invalid character was encountered. |
0x8007370D | ERROR_SXS_IDENTITY_PARSE_ERROR | An identity string is malformed. |
0x8007370B | ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME | The name of an attribute in an identity is not within the valid range. |
0x8007370A | ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE | The value of an attribute in an identity is not within the valid range. |
0x80070057 | ERROR_INVALID_PARAMETER | The parameter is incorrect. |
0x800B0100 | TRUST_E_NOSIGNATURE | No signature was present in the subject. |
0x80092003 | CRYPT_E_FILE_ERROR | An error occurred while Windows Update reads or writes to a file. |
0x800B0101 | CERT_E_EXPIRED | A required certificate is not within its validity period when verifying against the current system clock or the time stamp in the signed file. |
0x8007371B | ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE | One or more required members of the transaction are not present. |
0x80070490 | ERROR_NOT_FOUND | Windows could not search for new updates. |
0x800f0984 | PSFX_E_MATCHING_BINARY_MISSING | Matching component directory exist but binary missing |
0x800f0986 | PSFX_E_APPLY_FORWARD_DELTA_FAILED | Applying forward delta failed |
0x800f0982 | PSFX_E_MATCHING_COMPONENT_NOT_FOUND | Can't identify matching component for hydration |
Verify the integrity of resources
The System Update Readiness tool verifies the integrity of the following resources:
- Files that are located in the following directories:
- %SYSTEMROOT%\Servicing\Packages
- %SYSTEMROOT%\WinSxS\Manifests
- Registry data that is located under the following registry subkeys:
- HKEY_LOCAL_MACHINE\Components
- HKEY_LOCAL_MACHINE\Schema
- HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing
This list may be updated at any time.
When the System Update Readiness tool detects incorrect manifests, Cabinets, or registry data, it may replace the incorrect data with a corrected version.
Logging
The System Update Readiness tool creates a log file that captures any issues that the tool found or fixed. The log file is located here:
- %SYSTEMROOT%\Logs\CBS\CheckSUR.log
- %SYSTEMROOT%\Logs\CBS\CheckSUR.persist.log
How to fix errors that are found in the CheckSUR log file
To manually fix corruption errors that the System Update Readiness tool detects but can't fix, follow these steps:
Open %SYSTEMROOT%\Logs\CBS\CheckSUR.log.
Note
%SYSTEMROOT% is an environment variable that saves the folder in which Windows is installed. For example, generally the %SYSTEMROOT% folder is C:\Windows.
Identify the packages that the tool can't fix. For example, you may find the following in the log file:
Summary: Seconds executed: 264 Found 3 errors CBS MUM Missing Total Count: 3 Unavailable repair files: servicing\packages\Package_for_KB958690_sc_0~31bf3856ad364e35~amd64~~6.0.1.6.mum ...
In this case, the package that is corrupted is KB958690.
Download the package from Microsoft Download Center or Microsoft Update Catalog.
Copy the package [.msu] to the
%SYSTEMROOT%\CheckSUR\packages
directory. By default, this directory doesn't exist and you need to create the directory.Rerun the System Update Readiness tool.
If you are a technical professional, see How to fix errors found in the CheckSUR.log for a more option on fixing errors in the CheckSUR.log.