Dual boot - windows boots but can't login - Blurred screen then blue loop

1. Windows Boot Manager Not Detecting Windows Installations
   Your bootrec /scanos and bootrec /rebuildbcd commands reported 0 Windows installations found, which means the Boot Configuration Data (BCD) store is either missing or corrupted and not properly pointing to your Windows partition. This is likely why Windows fails to load login credentials and cycles through blurred screen to blue loop.
2. Fixing the BCD Store Manually
   You successfully ran bcdboot C:\windows which recreates boot files, but if the BCD store lacks correct entries or the EFI partition isn’t properly mounted, the problem persists.
   Steps to fix:
   • Boot into Windows recovery command prompt.
   • Use diskpart to assign a drive letter (say W to your EFI partition (usually a FAT32 partition around 100-500MB).
     Commands (DiskPart):
     
     Code:

     list disk
     select disk 0 (select your disk containing OS)
     list partition
     select partition X (EFI partition, FAT32)
     assign letter=W
     exit

   • Then rebuild boot files with:
     
     Code:

     cd /d W:\EFI\Microsoft\Boot
     bootrec /fixboot
     bcdboot C:\Windows /s W: /f UEFI

   • Reboot and test. This often resolves the "Access is denied" error on bootrec /fixboot and fixes boot issues caused by EFI partition problems.
3. Check BCD Entries and Set Default
   Run bcdedit /enum all to review entries. If {current} or {default} entries are missing or invalid, recreate them with commands like:
   
   Code:

   bcdedit /set {default} osdevice partition=C:
   bcdedit /set {default} device partition=C:
   bcdedit /set {default} path \Windows\system32\winload.efi
   bcdedit /set {default} description "Windows 11"
   bcdedit /set {bootmgr} displayorder {default}
   bcdedit /default {default}

   Make sure to replace C: with your actual Windows partition letter if different.
4. Check Windows Recovery Environment (WinRE)
   Sometimes Windows boots into the recovery environment instead of normal OS causing login issues with no password prompt. Run:
   
   Code:

   reagentc /info
   reagentc /enable

   To check and enable recovery environment if disabled.
5. Grub and Dual Boot Considerations
   Since you use dual boot with Ubuntu, the absence of GRUB menu could be due to Windows updates or EFI boot order issues. To restore GRUB:
   • Boot into Ubuntu (if possible) or use a live Ubuntu USB.
   • Run sudo update-grub to detect Windows and regenerate GRUB menu.
   • Use efibootmgr in Linux to check UEFI boot order and set Ubuntu GRUB loader as first if needed.
6. AOMEI Backupper and Boot Services
   You mentioned possible interference from AOMEI Backupper during boot. Backup tools can sometimes install boot-related files or services that interfere with normal boot. If you can, disable or uninstall AOMEI temporarily to test. Also, try booting Windows in Safe Mode (which you can do via recovery ISO) and uninstall recent updates or drivers that might cause boot loops.
7. If Problems Persist: In-Place Repair or Reinstall
   If none of the above succeed, as a last resort, use Windows 11 installation media for an in-place upgrade repair.
   • Choose Upgrade and Keep Files option, which repairs system files without losing data.

Key Observations​

1. BCD Structure Looks Healthy:
   Your BCD entries appear largely intact. The {default} entry points to partition=C: with the correct winload.efi path. Your Boot Manager and Boot Loader configurations look reasonable, and there’s no sign of missing or obviously invalid entries.
2. AOMEI Boot Entries:
   The extra Aomei PE and related device options are visible, but currently, they do not appear to be the default boot target, so their impact should now be minimal.
3. The Critical Loop:
   The fact that you see the Windows login background, but no password/PIN box, then a blue/fuzzy screen, then back to the background, suggests:
   • Windows is technically booting but encountering a critical failure at the credential provider or user profile load stage.
   • This is often seen in user profile corruption, system file corruption, or low-level driver/service load failures (sometimes triggered by third-party tools or failed updates).

Targeted Steps to Continue​

1. Offline User Profile and System File Repair​

a) Check for Corrupt User Profiles​

1. In the command prompt, load the Software and System registry hives:
   
   Code:

   reg load HKLM\tempsoft C:\Windows\System32\config\SOFTWARE
   reg load HKLM\tempsys C:\Windows\System32\config\SYSTEM

2. Check for third-party logon providers or issues under:
   reg query "HKLM\tempsoft\Microsoft\Windows NT\CurrentVersion\Winlogon"
   Look for suspicious Userinit, Shell, and GinaDLL.
   • Userinit should be: C:\Windows\system32\userinit.exe,
   • Shell should be: explorer.exe
   • GinaDLL should not exist in modern Windows.
   If any values are wrong, correct them with:
   
   Code:

   reg add "HKLM\tempsoft\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Userinit /t REG_SZ /d "C:\Windows\system32\userinit.exe," /f
   reg add "HKLM\tempsoft\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Shell /t REG_SZ /d explorer.exe /f
   reg delete "HKLM\tempsoft\Microsoft\Windows NT\CurrentVersion\Winlogon" /v GinaDLL /f

b) Attempt a System File Scan (SFC) from Recovery​

c) Check Disk/Partition Health​

d) Driver Check:​

2. Hidden User Profile Loop or Service (Rare but Possible)​

• Boot to recovery, enter the Offline Registry as above.
• Check for odd entries (third-party login provider, custom shell).
• If comfortable, try creating a temporary local admin user (Google “offline add user to Windows using registry”)—to use during login.

3. Safe Mode with Command Prompt​

   net user /add tempadmin P@ssw0rd!
   net localgroup administrators tempadmin /add

4. Repair Install Without Data Loss​

• Use a modern Windows 11 installer USB, boot it from within Windows (if possible), and choose “Upgrade” not “Custom."
• If you can only boot from outside, you may be forced into a “Custom” install, risking data/other OS loss. Back up data first if you try this.

If All Else Fails​

• From Ubuntu, back up your critical Windows data (the files remain accessible unless system encryption is used).
• After a full backup, you may be able to safely delete/rename the C:\Users\<user>\NTUSER.DAT files to force a new profile (as a last resort).

Final Note​

1. User Profile Corruption​

• Try to log in with another account or access Safe Mode.
• If you gain access, back up all important data from C:\Users\[corrupt-profile] (avoid copying system or hidden files).
• Create a new user account from Safe Mode or another admin account.
• Migrate your data (Documents, Desktop, Pictures, etc.) to the new profile—do not copy the full old profile folder to avoid propagating corruption.
• Consider running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to fix underlying system file problems before or after repair.

2. Graphics Driver Fault​

• Boot into Safe Mode.
• Uninstall and reinstall your graphics drivers using Device Manager or DDU (Display Driver Uninstaller).
• Download the latest drivers from your GPU manufacturer’s website.
• Reboot and check if the issue persists.

3. Disk or Permission Errors​

• From WinRE or Safe Mode, run chkdsk /f /r on the Windows partition.
• Use Event Viewer (eventvwr.msc) to look for disk or profile service errors.

Summary of Recovery Steps​

1. Try login in Safe Mode.
2. Test with another user profile.
3. Back up all irreplaceable data immediately.
4. Run repair tools:
   • sfc /scannow
   • DISM /Online /Cleanup-Image /RestoreHealth
   • chkdsk /f /r
5. Create a new user profile and transfer files.
6. Uninstall and reinstall graphics drivers.
7. If all else fails, use System Restore or Reset This PC (preserving files, if possible).

• Slow Boot After Recovery:
  This can sometimes happen if Safe Boot options were left enabled in msconfig, or if there are residual issues with startup drivers/services. Double-check that “Safe boot” and related flags are disabled in msconfig.
• Old User Profile Issues:
  If your previous user profile is still inaccessible or slow to load, it’s often best to migrate settings/files to your new user. Corruption in the user hive is a common cause of login and speed issues after a major recovery event.
• Startup Optimization:
  Use Task Manager’s Startup tab (Ctrl+Shift+Esc) to disable unnecessary startup programs. You can also run DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow from an admin Command Prompt to repair any lingering Windows file issues.
• Driver or Service Delays:
  Boot delays can also be caused by outdated drivers or missing services. Check Device Manager for yellow exclamation marks and update as needed.

Delete the User Profile via Registry Editor​

• Time each phase once:
  1) Power button → GRUB menu,
  2) select Windows → spinning dots,
  3) dots → sign‑in screen,
  4) sign‑in → desktop.
• Post the rough seconds for each; it tells us if the holdup is firmware/GRUB, Windows boot, or logon.

• Boot List: UEFI (not Legacy/CSM).
• Secure Boot: Enabled is preferred. Ubuntu’s shim is signed; if you use NVIDIA/proprietary drivers you may be asked to enroll a MOK on first Linux boot. If that’s a hassle, Disabled is fine functionally, but it’s not the reason for a slow boot.
• Legacy Option ROMs: Disabled.
• SATA Operation: AHCI is generally best unless you’re using Intel RST/RAID. If you’re currently “RAID On,” switching to AHCI can shave seconds, but do it safely:
  • In Windows: bcdedit /set {current} safeboot minimal
  • Reboot, enter BIOS, change to AHCI, save/exit.
  • Windows boots into Safe Mode; open admin CMD: bcdedit /deletevalue {current} safeboot
  • Reboot normally.
• Network/PXE boot: Disable as a boot option (or move it to the bottom). Same for optical/USB if you don’t need them during normal boots.
• Boot order: Keep “ubuntu” (shimx64.efi) first so GRUB shows, put “Windows Boot Manager” second. Remove stale/duplicate entries if your BIOS allows.

• In Ubuntu: edit /etc/default/grub
  • GRUB_TIMEOUT=2
  • GRUB_TIMEOUT_STYLE=menu
  • sudo update-grub
• In Windows (optional, if you ever see the Windows boot menu): bcdedit /timeout 0

• External drives and big USB disks: Unplug during a timing test. Firmware and Windows can stall probing them.
• RAW/Problem partitions: Your earlier DiskPart showed a RAW volume (I: ~299 GB). Windows can pause trying to mount/initialize it.
  • If you don’t need it in Windows: diskpart → select volume <n> → offline volume
  • Or format/initialize it properly in Disk Management if it’s meant to be used.
• AOMEI leftovers:
  • In Services (services.msc) and Task Scheduler, disable AOMEI services/tasks.
  • In an elevated CMD, remove orphaned BCD entries you no longer need (double‑check GUIDs first):
  • bcdedit /enum
  • bcdedit /delete {fd89e40b-48a0-4ef9-a6f6-f705281741a2}
  • Also delete the AOMEI “device options” GUIDs referencing \Aomei\AomeiBoot.sdi
• WinRE pointer refresh (fast, safe):
  • reagentc /disable
  • reagentc /enable

• Event Viewer boot diagnostics:
  • Event Viewer → Applications and Services Logs → Microsoft → Windows → Diagnostics‑Performance → Operational.
  • Look at Event ID 100 (Boot Performance Monitoring). Note “Boot Duration,” and expand the details—DriverInit, MainPathBoot, PostBoot, etc. Post a screenshot if you can; it pinpoints the phase that’s slow.
• Repair system files:
  • DISM /Online /Cleanup-Image /RestoreHealth
  • sfc /scannow
• Startup programs:
  • Task Manager → Startup tab → Disable anything non‑essential (backup tools, updaters, tray apps).
• Graphics and chipset drivers:
  • Install the latest Intel chipset/MEI and your GPU driver from Dell Support for your exact Inspiron model. Display stack issues can delay the sign‑in/desktop phases.
• Fast Startup (optional):
  • If you don’t mount your Windows partition from Ubuntu, enabling Fast Startup helps cold boots:
  • Control Panel → Power Options → Choose what the power buttons do → Turn on fast startup.
  • If you routinely access NTFS from Ubuntu, keep Fast Startup off to avoid hibernation/dirty‑bit conflicts.

• Boot logging: msconfig → Boot → check “Boot log”; after boot, review C:\Windows\ntbtlog.txt for drivers that take ages to load.
• Windows Performance Recorder (Boot) + Windows Performance Analyzer can give a definitive answer. If you want to go that route, I can give a quick capture recipe and read the .etl for you.

• Open an elevated Command Prompt:
  • reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v AutoAdminLogon /t REG_SZ /d 0 /f
  • reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultUserName /f
  • reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultPassword /f
• Optional: use Microsoft’s Sysinternals Autologon to explicitly set your new account, or disable autologon entirely.

• HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
• Ensure there’s no SID whose ProfileImagePath points to C:\Users\glenn. If one exists, and you truly don’t need it, delete that SID key.

• Scheduled Tasks:
  • schtasks /query /fo LIST /v | findstr /i "Run As User"
  • Re‑save any tasks that reference the old user, or delete them.
• Services running as the old user:
  • wmic service get Name,StartName | findstr /i glenn
  • Update any offenders to run as Local System/Network Service or your new account, as appropriate.
• Startup entries and paths:
  • Check HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run for paths under C:\Users\glenn
  • Check both Startup folders: shell:startup and shell:common startup
• Stored credentials:
  • cmdkey /list
  • Remove anything tied to the old account via Credential Manager or cmdkey /delete:target

• reagentc /disable
• reagentc /enable
• If you added or tested extra boot entries (e.g., AOMEI PE), you can prune them:
  • bcdedit /enum
  • bcdedit /delete {GUID} (only for entries you’re sure you no longer need)

• Boot mode: UEFI
• Secure Boot: Enabled is preferred; Ubuntu’s shim is signed. If you hit driver/MOK issues, Disabled is acceptable.
• Legacy Option ROMs: Disabled
• Keep “ubuntu” first (so GRUB shows), “Windows Boot Manager” second. Disable PXE/Network boot and other unused boot devices to shave a second or two.

• If you still have that RAW volume from earlier, either initialize/format it in Disk Management or set it Offline so Windows doesn’t pause probing it.
• Event Viewer → Microsoft → Windows → Diagnostics‑Performance → Operational → Event ID 100. If Boot Duration is high, check the breakdown (DriverInit, MainPathBoot, PostBoot) to pinpoint the slow phase and we can tune accordingly.
• Quick health sweep:
  • DISM /Online /Cleanup-Image /RestoreHealth
  • sfc /scannow

• Now that the system is clean and the new user is settled, take a full image backup. It’s the best insurance before future Windows or driver updates.

• If using Wi‑Fi: make sure Airplane mode is off and the physical Wi‑Fi switch (if present) is on.
• Try a wired Ethernet cable to your router. If Ethernet works, it narrows this to the wireless driver/settings.
• Reboot once (so services/drivers from your recent changes start clean).

• Open Device Manager (devmgmt.msc) → Network adapters.
  • Do you see your wireless or Ethernet adapter listed?
  • Any yellow exclamation marks or “Unknown device” entries?
  • If adapter is present but disabled: right‑click → Enable device.
• If it’s missing entirely, the driver may have been removed or disabled.

• ipconfig /all — see whether adapter has an IP, DHCP server, DNS, MAC address
• ping 8.8.8.8 — tests basic IP connectivity (bypasses DNS)
• ping google.com — tests DNS resolution
• netsh interface show interface — shows interface state
• netsh winsock reset
• netsh int ip reset
  Reboot after the two netsh resets and test again.

• DHCP Client
• DNS Client
• Network Connections
• Network Location Awareness
• Network List Service
• WLAN AutoConfig (for Wi‑Fi)
• Remote Procedure Call (RPC) — must be running
  If any service shows a “Log On As” value referencing the old/deleted user, change it to Local System:
• Right‑click service → Properties → Log On → Local System account → OK → restart service.

• From another PC download the correct drivers from Dell Support for your Inspiron model (chipset + network/Wi‑Fi driver). Put them on a USB stick.
• On your laptop run (in an elevated CMD) to install INF drivers directly:
  • pnputil -i -a "D:\drivers*.inf"
    Or from Device Manager: right‑click adapter (or Unknown Device) → Update driver → Browse my computer → choose the folder on USB → Install.
• If you only have driver executables (.exe), run them on the affected PC.

• netsh wlan show drivers — confirms if wireless driver is loaded and supported.
• If driver says radio is off, try: netsh interface set interface "Wi‑Fi" enabled
• Check the Wireless adapter Power Management: Device Manager → adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.”

• In elevated CMD:
  • netsh interface ip set address "Ethernet" dhcp
  • netsh interface ip set dns "Ethernet" dhcp
  • (replace "Ethernet" with the exact name shown by netsh interface show interface or by ipconfig)
• Or manually set a temporary static IP in the same subnet as your router to test.

• Copy/paste output of:
  • ipconfig /all
  • netsh interface show interface
  • netsh wlan show drivers (if Wi‑Fi)
  • Device Manager screenshot of Network adapters (or list printed via: pnputil /enum-devices /class Net)
• Note any error codes from the Windows Network Troubleshooter.

• Use Ubuntu (you said you dual boot) to download drivers and tools from Dell and copy them to Windows via USB. Or, boot Ubuntu and do the backup/image there if you’re comfortable (e.g., clonezilla, dd, or Gnome Disks can make an image). This gets your image saved even without Windows networking.

• Update Windows (Windows Update) and then run DISM /Online /Cleanup‑Image /RestoreHealth and sfc /scannow again.
• Create the full image backup right away.

• whether Ethernet works now,
• your Inspiron exact model (e.g., Inspiron 15 5000 series) or the network adapter shown in Device Manager,
  I’ll give the exact driver download link and step‑by‑step install commands you can use offline.

• Open an elevated Command Prompt (right‑click Start → Command Prompt (Admin) or PowerShell (Admin)) and run:
  • ipconfig /all
  • getmac /v
  • netsh interface show interface
  • wmic nic get Name,NetEnabled,NetConnectionStatus,DeviceID
• In PowerShell (Admin) you can also run:
  • Get-NetAdapter -IncludeHidden | Format-Table -AutoSize
    Copy/paste the outputs here if you want me to read them — they tell us whether Windows sees the NIC, has an IP, or is disabled.

• devmgmt.msc → View → Show hidden devices.
• Expand Network adapters and Other devices.
  • If you see your Realtek or “Unknown device” with a yellow triangle, right‑click → Uninstall device → check “Delete the driver software for this device” (only if you’re certain it’s the bad/old driver).
  • After removing, Action → Scan for hardware changes.
• If the adapter is present but disabled: right‑click → Enable device.

• In Admin CMD:
  • pnputil /enum-drivers
  • Note any Realtek or AOMEI related oemXX.inf entries.
  • To remove a bad driver: pnputil /delete-driver oemXX.inf /uninstall /force
    (Only delete known-bad vendor drivers. If unsure, paste pnputil output here.)

• From Ubuntu, download the correct Dell/Realtek driver for your Inspiron model (Realtek RTL8106E or the specific adapter shown in your screenshots).
• Copy the driver package (.zip/.exe/.inf) to a USB stick and in Windows:
  • Device Manager → right‑click adapter (or Unknown device) → Update driver → Browse my computer for drivers → Let me pick → Have Disk → point to the folder containing the .inf file.
• Or use pnputil to add the driver: (Admin CMD)
  • pnputil /add-driver "D:\Drivers*.inf" /install

• You said Secure Boot is disabled — that’s fine for unsigned drivers. If you later enable Secure Boot, signed drivers are required.
• If the driver package is an .exe, copy it to Windows and run it (may be a driver installer).

• In Admin CMD:
  • netsh winsock reset
  • netsh int ip reset
  • ipconfig /release
  • ipconfig /renew
  • ipconfig /flushdns
    Reboot and test.
• Check Services (services.msc): ensure these are Running/Automatic — DHCP Client, DNS Client, Network Connections, Network Location Awareness, WLAN AutoConfig (for Wi‑Fi), RPC.

• Settings → Network & Internet → Advanced network settings → Network reset.
• This reinstalls network adapters and resets settings (you’ll need to reinstall any special VPN drivers afterwards). Reboot after running it.

• Check BIOS: some laptops list an internal LAN/WLAN and can disable them. However, since Ubuntu sees the NIC, BIOS is probably OK.
• Use Device Manager → Action → Add legacy hardware → search for network adapter to try reinstalling manually.

• In Admin PowerShell:
  • dism /online /export-driver /destination:\DriverBackup
    This saves current drivers to D:\DriverBackup (change path as needed). Good to keep before you change things and useful for Clonezilla imaging.

• Tell me the exact Dell Inspiron model (found in your About screenshot), or paste the output of:
  • wmic csproduct get name, vendor, identifyingnumber
    I’ll point you to the precise Dell/Realtek driver and give step‑by‑step offline install instructions.

• Paste the output of ipconfig /all and Get-NetAdapter -IncludeHidden (or pnputil /enum-drivers).
• A quick screenshot of Device Manager → Network adapters (with View → Show hidden devices enabled).
• Your exact Inspiron model from About (if you want me to fetch the correct driver link).

• Ubuntu sees & uses the NIC (hardware and cabling are fine).
• In Windows the NIC does not appear at all (even with hidden devices shown).
• Realtek installer fails with the “Deep sleep mode / plug cable” error.
• You already tried device uninstall, driver store checks, netsh resets and Network Reset.
  => This is the classic Realtek “device has gone into deep/low-power state and Windows/installer doesn’t enumerate it” problem. There are three pragmatic paths I’d try next (ordered least invasive → most), plus a safe Ubuntu-based trick that frequently wakes the device so Windows can detect it.

1. Shutdown Windows completely (not Restart).
2. Unplug AC adapter. If you can remove the battery, remove it. If not removable, still unplug AC.
3. Press and hold the laptop power button for 30–60 seconds to fully discharge.
4. Reconnect AC (and battery), boot into Windows.
5. In Windows Device Manager → Action → Scan for hardware changes. Try the Realtek installer again (or Device Manager → Update driver → browse to the extracted INF folder).

1. Identify the Ethernet device and its PCI address:
   • sudo lspci -nnk | grep -iA3 ethernet
   • Note the PCI ID at the start of the line, e.g. 0000:02:00.0 — use whatever yours shows.
2. Try a device reset (replace 0000:02:00.0 with your device ID):
   • sudo su -
   • echo 1 > /sys/bus/pci/devices/0000:02:00.0/reset
   • sync
3. If the reset file doesn’t exist, try unbind/rebind the kernel driver (example for r8169 driver — match the driver name from lspci -nnk):
   • DRIVER=r8169 # change if your driver differs
   • DEV=0000:02:00.0 # change to your PCI ID
   • echo -n $DEV | sudo tee /sys/bus/pci/devices/$DEV/driver/unbind
   • echo -n $DEV | sudo tee /sys/bus/pci/drivers/$DRIVER/bind
4. Confirm the device still works in Ubuntu (ip a, ethtool <iface>), then fully power off and boot into Windows and check Device Manager / run the installer again.

1. Enter BIOS (F2 on most Dell) → look for any options related to NIC, LAN, Wake‑on‑LAN; toggle them (flip on/off), Save/Reboot.
2. If BIOS has a “LAN/Onboard NIC” enable/disable, ensure it’s Enabled.
3. If you’re comfortable: temporarily remove CMOS battery or use the BIOS “Restore defaults” / “Reset to defaults” option and reboot. (This is more invasive — do only if comfortable.)

• Use a cheap USB‑to‑Ethernet adapter or use an USB Wi‑Fi dongle in Windows — that will let you download the exact Dell Realtek driver/firmware and Windows updates. Then reattempt the device fixes above. This avoids wasting time while troubleshooting.

• Make sure you extract the driver package fully and point Device Manager → Update driver → Browse my computer → Let me pick → Have Disk → point to the .inf inside the extracted folder. The .exe installer often wraps the .inf; extracting first is critical.
• If the Realtek installer still reports deep sleep, try the power‑drain + immediate manual INF install sequence (do not run the install EXE until after a power drain and Device Manager scan).
• If you want, tell me the exact driver package name you downloaded and I’ll give the exact path to the .inf inside it.

• Output of Device Manager screenshot (you already attached one; if there’s any “Unknown devices” window show its details).
• From Ubuntu (while NIC working): output of:
  • sudo lspci -nnk | grep -iA3 ethernet
  • ip link show
  • sudo ethtool <interface-name> (replace <interface-name> with the NIC name like eno1)
• From Windows (if any traces appear): run in elevated CMD:
  • pnputil /enum-devices /class Net
  • pnputil /enum-drivers
    (You said pnputil shows none — that's telling and consistent with device not enumerated under Windows.)

• The Realtek “The Realtek Ethernet Controller was not found. If Deep Sleep Mode is enabled, please plug the cable” message is a common community symptom when the NIC is power‑stalled and/or the wrong driver is used; community fixes commonly used are the full power drain and PCI reset via Linux or toggling BIOS settings. See community threads discussing the same symptom. (forums.tomshardware.com, reddit.com)

• Select text:
  • Mouse: click at start, drag to end.
  • Keyboard: hold Shift and use arrow keys; or Ctrl+A selects all.
• To apply formatting:
  • Use the editor toolbar above the message box: highlight the text, then click Bold / Italic / Underline / Colour.
  • For BBCode manually: wrap text with tags. Examples:
  • Bold: bold text
  • Italic: italic
  • Colour: red text (replace red with color name or hex like #FF0000)
• Pasting from Word:
  • Paste as plain text: Ctrl+Shift+V (or use the “Paste as plain text” button) to remove hidden formatting, then apply forum formatting.
• If your forum editor doesn’t show color options, the forum may have color disabled—use * or , or attach a screenshot.