Patch Lady – Windows 10 versus 10 dealing with issues

Topic

New Reply

In the post Windows 7 era – if you are now dealing with Windows 10 there’s different ways to deal with issues. G. Winston Natoli shared this recap of
[See the full post at: Patch Lady – Windows 10 versus 10 dealing with issues]

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

jburk07, lmacri

Reply | Quote

Replies

“DISM is not available in Windows 7 and earlier.”
Well, it is on my Win 7 SP 1; it requires an elevated prompt.
I wouldn’t be surprised if the Win 10 version is new and improved.

Reply | Quote

PaulK wrote:

“DISM is not available in Windows 7 and earlier.”
Well, it is on my Win 7 SP 1; it requires an elevated prompt.
I wouldn’t be surprised if the Win 10 version is new and improved.

It would have been more accurate to say that DISM in Windows 7 does not have these repair options.

3 users thanked author for this post.

jburk07, PaulK, b

Reply | Quote

Is that limited feature set for DISM for all versions of Windows 7? And maybe Windows 7 Pro has more features enabled. For example Windows  7’s  System Image backups to a networked share(NAS) requires Windows 7 Pro and above as that option is not avail available to any Windows  7 Editions below Windows 7 Pro.

Reply | Quote

anonymous wrote:

Is that limited feature set for DISM for all versions of Windows 7?

Kirsty wrote:

MrBrian wrote:

Canadian Tech wrote:

Is DISM an available command on a Win7 Home system?

Yes.

DISM has limited functionality in Windows 7.

One link I came across when facing a Win7 rebuild recently (inspired by power failure during a thunderstorm) was helpful, and includes some details of 0x* error codes: Fix Windows Update errors by using the DISM or System Update Readiness tool

See: Deployment Image Servicing and Management Technical Reference

and: Deployment Image Servicing and Management Command-Line Options

1 user thanked author for this post.

jburk07

Reply | Quote

In the Win 1o world, a good monthly procedure is that after one successful reboot after applying the monthly core Win 10 update, to do cleanups by (1) using DISM to do a thorough cleanup of the SxS component store by a Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase command, and (2) using the external PatchCleaner utility to clean up the Installer folder.   Reasons:  (1)  reclaim several GB of storage, and (2) if it becomes necessary during the early days of a new monthly update to revert to the previous month, it is certainly better to revert back to your routine monthly Macrium Reflect clone of your Windows partitions (made monthly before you run a MS monthly update), which is trusted and complete, rather than use MS’s built in rollback capability (less trustworthy, has failed to rollback during problematic monthly updates).

Reply | Quote

Have you ever considered the possibility that you’re causing your own Windows 10 problems?

2 users thanked author for this post.

Kathy Stevens, b

Reply | Quote

Yes

Reply | Quote

Topic here is the capabilities of DISM for administering Win 10, for the specific audience of previous Win 7 administrators who may be unfamiliar with full DISM capabilities available in Win 10.   The post suggests using a specific DISM command monthly, to streamline Win 10 file set.  Not sure what Windows problems you’re referring to.  The rollback route advised in the posting enabled, for example, an easy recovery from the problematic Win 10 1607 upgrade, which damage partitions on our test machine (and left Win 10 unable to rollback with its built-in tools) — this was a widespread issue with that faulty Win 10 upgrade.

Reply | Quote