Search Results for '\"system image\'

If the device is working as intended, I would not loose sleep over the ‘repair installation procedure’ as it’s likely to be as Susan suggested, a driver, driver signing issue that’s blocked part of the repair.
Time is your friend, check your device oem drivers for updates frequently is my advice. Let us know what driver gets updated soon. In the mean time, I’d
check over your hardware for exclamation marks and such like in device manager and check over Event Viewer for red flags.

You can never have enough backups of personal files and system images FWIW

Windows - commercial by definition and now function...

1 user thanked author for this post.

Casey H

Casey H wrote:

As of now, the computer has no issues. *The BSOD that prompted me to do a repair in the first place has not resurfaced. As mentioned, updates seem to work, and I have several system images.

* my bolding for emphasis

Are you attempting to fix something that may have already been fixed?
By your own admission, it seems so. If your system integrity/ DISM reports are good , there’s nothing to worry about, just create a new image for good measure.

Windows - commercial by definition and now function...

1 user thanked author for this post.

Casey H

I was hoping this problem would go away after the September updates.  After your all-clear today, I went ahead with the September updates, which went through without a hitch.  I then tried the repair-install using a fresh iso file from MS.  I got the same error message today as before.

I tried 3 separate times without success.  I even deleted my Bluetooth mouse.  Only other thing I can think of is I also run Malwarebytes Premium.  In the past, I sometimes have needed to temporarily disable its active components for WIN 11 updates to proceed–not always, but sometimes.  My WIN 10 PC has never needed me to do that.  In addition to temporarily disabling the active features, I also closed the program before attempting to run the install.

I ran the installation from my Admin account and unticked the “unblock” property before mounting the iso file.

I’m concerned that I seem to be cut-off from the ability to do a repair install.  As of now, the computer has no issues.  The BSOD that prompted me to do a repair in the first place has not resurfaced.  As mentioned, updates seem to work, and I have several system images.  What would you think about restoring an older system image, then trying the repair-install.  Right now, both the August update and the September update has blocked me from running the program.

Casey

It appears that WuMgr is the popular alternative for when the wushowhide mechanism is retired. I have read Susan’s Topic 6000002 Guide to using WUMGR and understand how to download the portable version and make ready for use.

I am left with a bit of confusion as to how to proceed from there and have a few questions I hope someone can help with.

First, no mention is made by Susan of the need to do anything with the Options and Auto Update tabs in the lower left of WuMgr. Does that mean that those settings are fine as is as downloaded and extracted? No need to update anything on those tabs?

Next, I am curious as to what, if anything, needs to be done with Group Policy settings that may have been in use in conjunction with wushowhide. I can list several of the Group Policy choices that may have been enabled at one time or another (see my list below).

Do not include drivers with Windows Updates
Configure Automatic Updates
Select when Preview Builds and Feature Updates are received
Select when Quality Updates are received
Select the Target Feature Update version

Do any or all of these need to be returned to “Not enabled”? Will their presence affect the behavior of WuMgr in any way? Should any of the above Group Policies be retained?

Also a similar question regarding whether the network connection is set to “metered” or not? Would a “metered” setting need to be unset in order for WuMgr to function or is WuMgr function oblivious to that?

I actually have read a lot of posts beyond Susan’s initial WuMgr topic, but I just get more confused as to where the line is drawn between native Windows Update and the WuMgr tool. Please forgive whatever dense spots are making this hard for me. I have been using Group Policy along with wushowhide for so long with absolute success that I can’t shake my ingrained paradigms. While wushowhide may appear primitive, that is what made it so easy for me to understand.

My questions likely seem pretty dumb, so please be patient with them. I know I will need to move on from wushowhide. BTW – I have both Win10 Pro and Win11 Pro. And yes, I do use Macrium to create system images before allowing updates.

1 user thanked author for this post.

opti1

For those who wish to migrate from Win11 22H2 to 23H2 offline,
there is an ‘enablement package’ KB5027397 but it’s not
available via the MSFT catalog for download.

Below are the direct MS download links for respective systems.
Ensure you click the correct one for your system.

PREREQUISITS:
kb5031455 from October 2023 or a later CU
before applying this enablement package.

Remember to create a system image before any major OS updates

x86-64 LINK:
https://catalog.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/caa3ff4a-6420-4341-aeae-33b2d7f463be/public/windows11.0-kb5027397-x64_3a9c368e239bb928c32a790cf1663338d2cad472.msu

ARM64 LINK:
https://catalog.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/c29dd4ea-7f6a-4636-a991-29ba8ae70658/public/windows11.0-kb5027397-arm64_bacb74fba9077a5b7ae2f74a3ebb0b506f9708f3.msu

Restart required post patching..

Windows - commercial by definition and now function...

1 user thanked author for this post.

deuxbits

In the first Susan Bradley article on this subject #2689954 (dated July 23, 2024):

#2691368 Mike W (me) wrote:

Windows 10 22H2 – Local Microsoft Account – Windows Updates paused until 8/13/24

I am a general user without any PC technical knowledge or expertise.  I follow your instructions if they are easy and don’t require expert technical knowledge.

Drive Encryption is ON.  I have the option to turn it OFF.

BitLocker is ON.  I have the option to turn it OFF.

I have my BitLocker Recovery Key

Should I turn BitLocker OFF and/or turn Drive Encryption OFF (after Susan Bradley changes the DEFCON to ok to allow July Windows updates)?

Is this a simple matter of just turning BitLocker OFF and/or Drive Encryption OFF to install the July Windows Updates?

If I turn BitLocker OFF and/or Drive Encrypton OFF, will it be easy to turn them back ON after the July Windows updates are installed, without having to go through any challenging technical procedure to turn them back ON?

I’m looking forward to the next Susan Bradley advice about this issue.

Thank you for your help.

#2691528 – Susan Bradley replied:

If you know where your recovery key is, and you want bitlocker, I wouldn’t turn it off merely to install updates.  In my personal testing it has not triggered asking for the recovery key.

#2692781 –  Mike W replied:

I have my BitLocker Recovery Key from my Microsoft Account.  What method is used if I need to provide my BitLocker Recovery Key?  Will I simply be asked to type my 48-digit Recovery Key or is some other technical method used to provide the Recovery Key?

#2692788 – Susan Bradley replied:

Just manually type it in.

 

CURRENT STATUS: As always, I will back up my data and create a System Image before installing Windows Updates.  I am going to be brave and follow Susan Bradley’s advice.  I am not going to turn Encryption Off and not turn BitLocker Off.  I am going to install the July Windows Update and hope that the BitLocker Recovery Screen does not appear.  If it appears, I will enter my BitLocker Recovery Key and hope that it works.

In addition to following Susan Bardley’s advice, I am taking this approach because I do not want BitLocker to create a different BitLocker Recovery Key if I BitLocker is ever turned  back on again.

 

QUESTION: Is there ANYONE who installed the July Windows Update with Encryption ON and BitLocker ON who did NOT get the BitLocker Recovery Screen?

PKCano – You have helped me a lot on other issues.  What do you think about the approach that I will take based on Susan Bradley’s advice?

1 user thanked author for this post.

Tony_S

nOads,

I used 2 third party software downloads one being the MiniTool Partition Wizard.  Apparently there’s an operator error at my end.  I shall go back to class and try again!

I do have a fresh System Image Backup and MacriumReflect8/AcronisTrueImage backups living on my external hard drive.  Tested my boot into recovery media this AM just to be sure.  Thank you!

Bill T

 

PKCano wrote:

Windows Updates are cumulative. What’s in this month’s update will also be in next month’s update.

Surely, this cannot be correct when there is a major problem in an update?

As I stated in #2692135, I don’t have any recovery keys for my Windows 10 22H2 Pro system. So, if I install KB5040427 (the 2024-07 CU) and encounter the BitLocker problem, yes, I can restore my system from a system image. However, if what you say is true, I’m never going to be able to install another Windows update again because I will always encounter the same problem!

In the KB article for KB5040427, Microsoft do state, “We are investigating the issue and will provide an update when more information is available.”.  I am assuming therefore that, at some point, the issue will be corrected in KB5040427, and hence in subsequent updates. I’m minded to wait until that happens unless someone can reassure me that my system is immune from the BitLocker problem.

1 user thanked author for this post.

LHiggins

Yabba-Dabba-Doo!   The new release looks good with many updates and new features (see link below), all built on the new Ubuntu 24.04 package base.

https://www.linuxmint.com/rel_wilma_whatsnew.php

I’m tempted to upgrade from 21.2 when the official release comes out (after taking a system image with Foxclone). But I think I’ll wait until the next 22.x point release (usually released at the end of the year) and then do a clean install instead.

Same here on two Dell Inspiron 3670 desktop PC’s with Linux Mint 21.2. Ever since switching to Linux Mint almost 1.5 years ago, I have always installed all updates that come through the Update Manager and never had an issue. But prior to installing any updates, it is recommended to take a Timeshift snapshot so you always have something to fall back on if needed. Or in my case instead of Timeshift, I use Foxclone (Linux equivalent to Macrium Reflect) to create a system image.

Edit: also wanted to add that the Linux Mint forums are an excellent resource. I have learned a lot just by frequently browsing/reading the forum using the link below. There are also many other very friendly and experienced users of Linux Mint if you decide to create a post asking for help with something.

https://forums.linuxmint.com/search.php?search_id=active_topics

4 users thanked author for this post.

bassmanzam, Charlie, SueW, DrBonzo

sahalen wrote:

I have checked my crash dump files (*.dmp) and there aren’t any for the issue and date of occurrence.

Check that it’s set up…

https://www.askwoody.com/forums/topic/random-bsod/#post-2665177

When you get a crash dump, follow the Sysnative BSOD Posting Instructions and start a thread there.

sahalen wrote:

I save both the Windows Backup and Restore and Macrium Reflect system images to drives M: and N:. These are both Western Digital, removal, USB drives.

In the meantime, run chkdsk /r and the SeaTools Long Generic Test on those two drives.

 

Thank you for your immediate response.  I haven’t tried your recent recommendation yet but I will let you know when I do.  I have checked my crash dump files (*.dmp) and there aren’t any for the issue and date of occurrence. Summarizing my system, I save both the Windows Backup and Restore and Macrium Reflect system images to drives M: and N:.  These are both Western Digital, removal, USB drives. I first always save a Windows image to M: then to N:.  I next do the same with Macrium Reflect, but recently I have been getting an error that it can’t proceed. When I try to reboot, I get the BSOD. I have tried Macrium alone and it proceeds normally without issues.

Hi OldNavyGuy,

I want to inform you on the status of this. As mentioned, your command prompt instructions worked and I got back into my system. I then ran both memtest86 (per your suggestion) and Windows Memory Diagnostics and both showed failure. I then removed the 2 (of 4) older memory modules and both tests then passed. I replaced the 2 older modules with 2 newer ones and both tests again passed. This seemingly pointed to the bad memory as the cause of my system failure.

However, I just made a system image using Windows Backup and Restore (Windows 7) and I got the system error again right after it completed. This seems to point to Backup and restore as the culprit. I have been using this for years now without difficulties. However, I also use Macrium Reflect to make system images. This is working without problems.

Let me point out that the “diskpart”, “list volume” commands show all my hard drive volumes as “Healthy” (see attachment). Rerunning the memory tests with the 2 new modules (4 total) show no problems.

Do you have any thoughts why it seems that the Windows Backup and Restore is causing this problem? Again, I have been using this for years now without any problems until recently. Also, I continue to use Macrium Reflect without problems.

SheltieMom wrote:

that missing kernel message appeared when I tried to boot into the Macrium recovery as part of restoring the system image.

My mistake…

The instructions won’t help with the Macrium rescue drive…try rebuilding it on another computer.

 

 

OK, Old Navy Guy. What will happen when I reboot? (Or, what is it that your commands SHOULD give me?) I know it was disjointed because Woody didn’t recognize the “new” browser here — that missing kernel message appeared when I tried to boot into the Macrium recovery as part of restoring the system image.

Since the UConn women’s basketball game is less than an hour away, I will do this tomorrow. Thank you for your help!

Pat in CT
@sheltiemom