Rendered Unbootable On Windows 10


Author
Message
RevJimB
RevJimB
New Member
New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)
Group: Forum Members
Posts: 8, Visits: 23
I applied latest patch today and rebooted. I am looping, unable to finish boot. 
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)
Group: Forum Members
Posts: 4K, Visits: 29K
If you have a recent Reflect backup, booting into Rescue and restoring from that is probably the easiest way forward here.  If your current disk state has important data that wasn't captured in your most recent backup, then while booted into Rescue you can first create a new backup of your disk in its current unbootable state just to capture that data before restoring your most recent good backup, then mount that unbootable backup later to extract whatever files you need from it.  If you don't have any good backups to restore from, if you can get into the Windows Recovery environment, you may be able to use Microsoft's own System Restore function.

And to confirm, the patch you're referring to is a Reflect patch, namely V7.1.2833?  And are you seeing a blue screen or anything that might contain information that would help diagnose underlying cause?

Edited 18 January 2018 3:40 PM by jphughan
RevJimB
RevJimB
New Member
New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)
Group: Forum Members
Posts: 8, Visits: 23
jphughan - 18 January 2018 3:38 PM
If you have a recent Reflect backup, booting into Rescue and restoring from that is probably the easiest way forward here.  If your current disk state has important data that wasn't captured in your most recent backup, then while booted into Rescue you can first create a new backup of your disk in its current unbootable state just to capture that data before restoring your most recent good backup, then mount that unbootable backup later to extract whatever files you need from it.  If you don't have any good backups to restore from, if you can get into the Windows Recovery environment, you may be able to use Microsoft's own System Restore function.

And to confirm, the patch you're referring to is a Reflect patch, namely V7.1.2833?  And are you seeing a blue screen or anything that might contain information that would help diagnose underlying cause?

I didn't want to go to full restore, but was forced into it. I couldn't even get into safe mode through the Windows 10 recovery environment. Yes it was 2833. What is my path forward though if the update can't be loaded?
Nick
Nick
Macrium Representative
Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)
Group: Administrators
Posts: 1.7K, Visits: 9.2K
RevJimB - 18 January 2018 3:48 PM
jphughan - 18 January 2018 3:38 PM
If you have a recent Reflect backup, booting into Rescue and restoring from that is probably the easiest way forward here.  If your current disk state has important data that wasn't captured in your most recent backup, then while booted into Rescue you can first create a new backup of your disk in its current unbootable state just to capture that data before restoring your most recent good backup, then mount that unbootable backup later to extract whatever files you need from it.  If you don't have any good backups to restore from, if you can get into the Windows Recovery environment, you may be able to use Microsoft's own System Restore function.

And to confirm, the patch you're referring to is a Reflect patch, namely V7.1.2833?  And are you seeing a blue screen or anything that might contain information that would help diagnose underlying cause?

I didn't want to go to full restore, but was forced into it. I couldn't even get into safe mode through the Windows 10 recovery environment. Yes it was 2833. What is my path forward though if the update can't be loaded?

Are you running the latest Insider Preview version of Windows 10?

Kind Regards

Nick - Macrium Support

RevJimB
RevJimB
New Member
New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)
Group: Forum Members
Posts: 8, Visits: 23
Windows 10 Pro Version 1709 OS build 16299.192
Nick
Nick
Macrium Representative
Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)
Group: Administrators
Posts: 1.7K, Visits: 9.2K
RevJimB - 18 January 2018 5:04 PM
Windows 10 Pro Version 1709 OS build 16299.192

Hmm, that's very strange, there's nothing that should cause your experience in the Reflect install or patch. What Anti-Virus software are you running?

Can you download and install the Full installer using the instructions here:

https://knowledgebase.macrium.com/display/KNOW7/Installing+Macrium+Reflect

Kind Regards

Nick - Macrium Support

RevJimB
RevJimB
New Member
New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)New Member (11 reputation)
Group: Forum Members
Posts: 8, Visits: 23
This problem was actually an inaccessible boot device introduced by January Windows Updates on some machines with AMD processors.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search