Network disconnected rescue mode


Author
Message
Flam
Flam
New Member
New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)
Group: Awaiting Activation
Posts: 9, Visits: 16
I can no longer access my backup images on my network when in the Windows PE environment.
  • Network configuration shows "Network Disconnected"
  • There are no "other devices" listed.
  • Cannot browse to network (NAS) location
  • Windows version: 20H2 (OS Build 19042-421)

Thanks for any help
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)
Group: Forum Members
Posts: 7.6K, Visits: 54K
You say you can "no longer" access the network.  So what changed since you could?  You mention you're using the "Windows PE" environment, but you also mention a Build 19042.  If that's the Windows build of the actual Rescue Media environment rather than just your main Windows environment, then that is newer than the PE version that Reflect currently uses when you select WinPE 10 (which is 1709) and also newer than Windows 10 2004's build of 19041.  This would in turn suggest that you are both a) using Windows RE rather than Windows PE, and b) running a Windows Insider build.

If you're running an Insider build as your main Windows environment, you might want to consider using Windows PE 10 as your Base WIM for Rescue Media, which you can specify in Rescue Media Builder under Advanced > Choose Base WIM.  You will give up WiFi support, however, since that's only available when building with WinRE.  If you need WiFi rather than just Ethernet in Rescue Media, then you might want to consider building Rescue Media from a system that is not running an Insider build of Windows so that you're not essentially building something as crucial as Rescue Media on top of a beta environment.

Flam
Flam
New Member
New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)
Group: Awaiting Activation
Posts: 9, Visits: 16
jphughan - 26 July 2020 10:54 PM
You say you can "no longer" access the network.  So what changed since you could?  You mention you're using the "Windows PE" environment, but you also mention a Build 19042.  If that's the Windows build of the actual Rescue Media environment rather than just your main Windows environment, then that is newer than the PE version that Reflect currently uses when you select WinPE 10 (which is 1709) and also newer than Windows 10 2004's build of 19041.  This would in turn suggest that you are both a) using Windows RE rather than Windows PE, and b) running a Windows Insider build.

If you're running an Insider build as your main Windows environment, you might want to consider using Windows PE 10 as your Base WIM for Rescue Media, which you can specify in Rescue Media Builder under Advanced > Choose Base WIM.  You will give up WiFi support, however, since that's only available when building with WinRE.  If you need WiFi rather than just Ethernet in Rescue Media, then you might want to consider building Rescue Media from a system that is not running an Insider build of Windows so that you're not essentially building something as crucial as Rescue Media on top of a beta environment.

Thanks for your response!
Indeed, the Windows build I refer to is an insider build. My current PE is, "Windows PE 10 Release 1709 (64-bit). I access via boot loader option. 
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)
Group: Forum Members
Posts: 7.6K, Visits: 54K
Ok, so again, what changed since you were last able to use the network?  And are you sure network connectivity is completely broken?  For example, have you tried opening Command Prompt in Rescue (available from the taskbar) and running ipconfig, or pinging an IP address?

Flam
Flam
New Member
New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)
Group: Awaiting Activation
Posts: 9, Visits: 16
jphughan - 27 July 2020 1:34 PM
Ok, so again, what changed since you were last able to use the network?  And are you sure network connectivity is completely broken?  For example, have you tried opening Command Prompt in Rescue (available from the taskbar) and running ipconfig, or pinging an IP address?
As I rarely have occasion to need to restore, it has been quite some time since I last attempted. So, the change would be Windows 10 insider build(s).
Yes, I have tried accessing network from cmd, both from the rescue as well as Windows recovery environments, and there is no network available.
As this is most likely related to OS, my hope is that others have encountered the same issue and found a fix. I have searched and have not found anything.
Thanks again for your responses!
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)
Group: Forum Members
Posts: 7.6K, Visits: 54K
Happy to help!

Ok, if you're using WinPE 10 1709, then a change to your main OS normally wouldn't be relevant.  It normally WOULD be if you were building Rescue Media using WinRE, which causes Rescue Media to be built from an environment on the system's Recovery partition, which would in turn use the same Windows kernel as the "main" Windows environment.  But you're using WinPE 10, which causes Reflect to build Rescue Media on (currently) WinPE 10 1709, regardless of what your main Windows environment is running, and PE 10 1709 has been used as the WinPE 10 build choice since Reflect 7.2.  The only possible explanation I can come up with for why an OS change might have affected your Rescue Media even in this case is that if Reflect determines that certain hardware isn't natively supported by the Windows PE/RE build you're using for Rescue Media, it copies drivers out of the host OS to bake them into Rescue Media to add that support.  So I'm wondering if whatever network driver you're running on your Insider build might not be compatible with the older WinPE 10 1709 kernel.  Just to confirm, when you said in your original post that there are no "other devices" listed, do you mean that you clicked the Restore menu (not tab) and selected View Unsupported Devices, and Reflect didn't list anything?  In that case, it sounds like a network driver that is SUPPOSED to be appropriate for your network adapter was loaded, but it isn't working properly.  I've helped a couple people here who observed that problem with some storage controllers, i.e. driver loaded but no storage visible.  If that's what happened, the workaround would be to manually put a suitable network driver package into your Rescue Media build folder, specifically "C:\boot\macrium\WA10KDrivers\64Bit\Ethernet".  You might need to delete an existing driver there, then create a new folder (name doesn't matter) and copy the driver files of a suitable release into there.  You'd probably have to get that from the website of the system or network adapter vendor.  Then rebuild your Rescue Media and retest.

If on the other hand the View Unsupported Devices interface DOES show a network adapter, it means that a driver isn't being loaded at all. In that case, adding a suitable driver as I just described should still fix that.

Flam
Flam
New Member
New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)
Group: Awaiting Activation
Posts: 9, Visits: 16
jphughan - 27 July 2020 3:35 PM
Happy to help!

Ok, if you're using WinPE 10 1709, then a change to your main OS normally wouldn't be relevant.  It normally WOULD be if you were building Rescue Media using WinRE, which causes Rescue Media to be built from an environment on the system's Recovery partition, which would in turn use the same Windows kernel as the "main" Windows environment.  But you're using WinPE 10, which causes Reflect to build Rescue Media on (currently) WinPE 10 1709, regardless of what your main Windows environment is running, and PE 10 1709 has been used as the WinPE 10 build choice since Reflect 7.2.  The only possible explanation I can come up with for why an OS change might have affected your Rescue Media even in this case is that if Reflect determines that certain hardware isn't natively supported by the Windows PE/RE build you're using for Rescue Media, it copies drivers out of the host OS to bake them into Rescue Media to add that support.  So I'm wondering if whatever network driver you're running on your Insider build might not be compatible with the older WinPE 10 1709 kernel.  Just to confirm, when you said in your original post that there are no "other devices" listed, do you mean that you clicked the Restore menu (not tab) and selected View Unsupported Devices, and Reflect didn't list anything?  In that case, it sounds like a network driver that is SUPPOSED to be appropriate for your network adapter was loaded, but it isn't working properly.  I've helped a couple people here who observed that problem with some storage controllers, i.e. driver loaded but no storage visible.  If that's what happened, the workaround would be to manually put a suitable network driver package into your Rescue Media build folder, specifically "C:\boot\macrium\WA10KDrivers\64Bit\Ethernet".  You might need to delete an existing driver there, then create a new folder (name doesn't matter) and copy the driver files of a suitable release into there.  You'd probably have to get that from the website of the system or network adapter vendor.  Then rebuild your Rescue Media and retest.

If on the other hand the View Unsupported Devices interface DOES show a network adapter, it means that a driver isn't being loaded at all. In that case, adding a suitable driver as I just described should still fix that.

Thanks again!
I downloaded the drivers (3 files) and added them to the network folder. I chose to update the rescue environment - it indicated new drivers - I then booted into the Win PE environment - sadly, no change. 
After going back to Windows I again attempted to update rescue by manually browsing to the Drivers..../Ethernet folder. 
I chose "scan". the resulting dialog reads, "No updated driver found. The best driver is already set for this device".
I then created a boot CD, with the same result.
I believe the drivers are loading but the issue  Has to do with "Media disconnected" when I run ipconfig. Here are a couple of screen shots.

jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)
Group: Forum Members
Posts: 7.6K, Visits: 54K
Well a picture is worth 1000 words.  Yes, that indicates that the driver is indeed loading properly.  If what you posted in those screenshots is what you've been seeing all along, then those would have been worth posting upfront, since that might have saved a trip down a rabbit hole. Smile  But you're saying that the network adapter shows as Disconnected in Rescue even though it shows as connected in full Windows?  Just as a sanity check, for that adapter labeled Ethernet in the ipconfig output from within Rescue, can you note down its MAC Address and make sure that the network adapter that actually works in Windows is using the same MAC Address?  If you're finding that the exact same Ethernet adapter with the same MAC Address is showing as connected and functional in full Windows but shows as Disconnected in Windows PE, I'm not sure what to suggest.  I've never seen that happen when the driver has been loaded and the adapter is shown in ipconfig output.

Flam
Flam
New Member
New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)New Member (10 reputation)
Group: Awaiting Activation
Posts: 9, Visits: 16
jphughan - 27 July 2020 8:19 PM
Well a picture is worth 1000 words.  Yes, that indicates that the driver is indeed loading properly.  If what you posted in those screenshots is what you've been seeing all along, then those would have been worth posting upfront, since that might have saved a trip down a rabbit hole. Smile  But you're saying that the network adapter shows as Disconnected in Rescue even though it shows as connected in full Windows?  Just as a sanity check, for that adapter labeled Ethernet in the ipconfig output from within Rescue, can you note down its MAC Address and make sure that the network adapter that actually works in Windows is using the same MAC Address?  If you're finding that the exact same Ethernet adapter with the same MAC Address is showing as connected and functional in full Windows but shows as Disconnected in Windows PE, I'm not sure what to suggest.  I've never seen that happen when the driver has been loaded and the adapter is shown in ipconfig output.

Sorry for the rabbit hole - Yes, this is what I have been seeing all along.
I verified that the MAC Address in Windows and Rescue are identical.
My workaround is to use a USB connected external HDD for backups. Of course, I much prefer using my NAS.
Thanks again for your suggestions. This is indeed odd.
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)Macrium Evangelist (11K reputation)
Group: Forum Members
Posts: 7.6K, Visits: 54K
Just as a really long shot, what happens if you disconnect and reconnect the network cable after the driver has loaded?  Any change?  And do you see an actual link light active at the port, assuming your Ethernet interface even has one?  Or if not, do you have a link light at the switch port or whatever device is on the other end of that cable?

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search