Windows Update Common Corruption Error Code and its Description

Code	Error	Description
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

Create Configuration Manager Collection based on Heartbeat DDR

 We'll look at how to create a Device collection that will display clients who haven't reported back to Configuration Manager in 14 days based on the client Heartbeat DDR agent date.

To find configuration manager clients that aren't sending heartbeat DDR older than 14 days, copy the below query to create a device collection. You can also change the 14 days to any number of days based on your office's needs.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ResourceId not in (select ResourceID from SMS_R_System where AgentName in ("Heartbeat Discovery") and DATEDIFF(day,AgentTime,GetDate())<14)

Feature Update to Windows 10 Version 21H2 x64-based systems 2021-11 via Enablement Package

Here are the download links for the update mentioned in the title.

System requirements from Microsoft:

KB5003791: Update to Windows 10, version 21H2 by using an enablement package

Windows Build number: 19041/19042/19043.1237 or higher.

Download the package and install it with a double click on the file.

x64: http://b1.download.windowsupdate.com/d/upgr/2021/11/windows10.0-kb5003791-x64_14e7547b08f1b29cae6e41c9f7da5f1347d9955c.msu

Name: windows10.0-kb5003791-x64_14e7547b08f1b29cae6e41c9f7da5f1347d9955c.msu
Size: 168099 bytes (164 KiB)
CRC32: A83F3B3A
CRC64: 72F8B925467B2CD8
SHA256: A51288BDE7C8228C3244FEA5AA7BC7DB1A014E48EAAF7DC1DC04A16A2E45C0DF
SHA1: 14E7547B08F1B29CAE6E41C9F7DA5F1347D9955C
BLAKE2sp: 85D747995B03CEC0A18D2E23649FE05C7D2D64D277ECC0FFE7AC0A00117A3DE5

x86: http://b1.download.windowsupdate.com/d/upgr/2021/11/windows10.0-kb5003791-x86_ac1fc53b104c6ce0ffa50b70af754b81e56829ce.msu

Name: windows10.0-kb5003791-x86_ac1fc53b104c6ce0ffa50b70af754b81e56829ce.msu
Size: 168642 bytes (164 KiB)
CRC32: F0C57E17
CRC64: 304DC7C229403463
SHA256: 4C7F1F715FC335AA046E4BF6667B69B6B0512426F03792BBCA3262B486D128CE
SHA1: AC1FC53B104C6CE0FFA50B70AF754B81E56829CE
BLAKE2sp: 84A45BC25ABE3C9271F6FDD89DFE79CEA0D886D81E88E845AF5CE52F347063AD

arm64: http://b1.download.windowsupdate.com/d/upgr/2021/11/windows10.0-kb5003791-arm64_047071577e1aa33883b851a8b2c749b1e723e369.msu

Name: windows10.0-kb5003791-arm64_047071577e1aa33883b851a8b2c749b1e723e369.msu
Size: 168718 bytes (164 KiB)
CRC32: 85C4ACF6
CRC64: 1050BF8A799234A2
SHA256: 79689953E8B3E542B08C788E760BD9BDFBBCB3AF7D9E29ECEB9AC3FDBDF1DA79
SHA1: 047071577E1AA33883B851A8B2C749B1E723E369
BLAKE2sp: B5192D05461BEBAA91B2482ADEAA12727B4FB63A22FBFABD069FBACD9D4F292E

Introducing the next feature update to Windows 10: 21H2 | Windows Experience Blog

More information can be found in the following post:

https://www.reddit.com/r/Windows10/comments/qvenhp/windows_10_21h2_19044_launch_megathread/

Rev. 3 - Link to megathread added.

Difference between x86, x64 and ARM architecture

Both x86 and x64 are same CPU architecture. HOW?

x86 is a "CPU" architecture which was initially used with 16bit "chip" and later on extended to be used on 32 bit chip. For most of the time, we used a 32bit chip(each number represented with 32 bits) that had x86 architecture. So basically, when we said this computer (CPU) is x86, it meant 32 bit or vice versa and same with OS, if an OS was 32bit, then it meant it was running x86 CPU architecture chip. (I'm not considering ARM here)

Now, due to the limitation of memory usage with 32bit chip that it can only support 4GB of RAM, x86 was then extended to be used on 64 bit chip, so basically now the same architecture (instructions set) was used to build a chip that used 64bit to represent a number, hence 64bit chip. Initially it was called x86-64 and later reduced to x64 which meant that x86 is the architecture on a 64bit chip.

Like x86 and x64, ARM is a different processor (CPU) architecture. The ARM architecture is typically used to build CPUs for a mobile device, ARM64 is simply an extension or evolution of the ARM architecture that supports 64-bit processing. Devices built on the ARM64 architecture include desktop PCs, mobile devices, and some IoT Core devices (Rasperry Pi 2, Raspberry Pi 3, and DragonBoard). For example the Microsoft HoloLens 2 uses an ARM64 processor.

About the architectures, you can refer to this document.

Command to hide and unhide the folder

 

Microsoft Intune Policy Refresh Intervals

What are the policy refresh intervals for the various device platforms in Microsoft Intune?

1. iOS - Every 8hrs
2. Android - Every 8hrs
3. Windows Phone - Every 8hrs
4. Windows PCs - Every 24hrs

In addition to the above-mentioned policy update intervals, if the device was recently enrolled in Microsoft Intune, there are a few other intervals worth mentioning:

1. iOS - Every 15 minutes for 6 hours and then every 6 hours
2. Android - Every 3 minutes for 15 minutes then every 15 minutes for 2 hours, and then every 8 hours
3. Windows Phone - Every 5 minutes for 15 minutes then every 15 minutes for 2 hours, and then every 8 hours
4. Windows PCs enrolled as devices - Every 3 minutes for 30 minutes, and then every 24 hours

Reference: https://docs.microsoft.com/en-us/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned