Share via

Can’t boot to Windows 11, appeared after a windows update, get the message Couldn’t connect to the network, log file J:windows\system32\logfi

Gwyn Williams 0 Reputation points
2026-05-05T07:23:35.21+00:00

Can’t boot to windows the bitlocker screen appears, after trying repair options the message Couldn’t connect to the network Log file J:\windows\system32\logfiles\str\strtrail.txt. I did not create the J: directory or the files that should be on the C: drive. I can access the J: drive from the cod, and open files with notepad from the cmd, the J: drive doesn’t exist in the BIOS, how can this problem be fixed

Windows for home | Windows 11 | Recovery and backup
0 comments No comments

3 answers

Sort by: Most helpful
  1. DaveM121 872.6K Reputation points Independent Advisor
    2026-05-05T07:57:59.36+00:00

    If you have tried all available options in the Recovery Environment, including uninstalling the latest update, System Restore... etc. and no option is recovering your system, then you will need to create a bootable Windows 11 USB on another working PC and boot your PC from that, then rather than installing Windows 11, select ‘Repair this Computer’ that will give you access to the Recovery Environment from there

    In the Recovery Environment on the USB, try each available option.

    Click this link:  https://www.microsoft.com/software-download/windows11

    to download the Media Creation Tool to create the bootable USB.

    Then, boot your PC from the Installation Media you just created.


  2. Gwyn Williams 0 Reputation points
    2026-05-05T07:43:36.1933333+00:00

    I’ve entered the correct bitlocker key have tried safe mode, same failure, I’ve tried all the repair text from the cmd, also there is no connection to the router. The messages all point to corrupt files. I feel my only option is a new hardrive and reinstall windows to avoid loss of data.

    0 comments No comments

  3. Q&A Assist
    2026-05-05T07:23:47.97+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The J: drive that appears in the recovery environment is normal: Windows PE often assigns different letters than the running OS, so the Windows partition that is C: during normal operation can appear as J: when booted into recovery. The issue is not the J: drive itself but that Windows cannot complete boot after the update and BitLocker is blocking access.

    To recover the system and boot Windows again, follow these steps in order:

    1. Provide the BitLocker recovery key
      When the BitLocker screen appears, enter the BitLocker recovery key for the system drive. If the key is not available, it must be retrieved; otherwise, the drive cannot be unlocked and the only option is to erase and reinstall Windows. The BitLocker recovery key is associated with the Microsoft account used on the device. It can be retrieved by signing in to the Microsoft account on another device and checking the recovery keys as described in the BitLocker recovery key article. If the key is not present there or in any printed/USB backup, the encrypted data cannot be recovered and the drive must be formatted and Windows reinstalled.
    2. After unlocking, try normal boot and Safe Mode
      Once the drive is unlocked with the recovery key, allow the system to continue booting. If Windows still fails to start normally, use Advanced Startup → Troubleshoot → Advanced options → Startup Settings and attempt to boot into Safe Mode. If Safe Mode works, restart again from Safe Mode to see if normal boot is restored.
    3. If Windows still will not start
      If the system remains unbootable even after providing the BitLocker key and trying Safe Mode, and there is no working restore point or backup, the remaining option is to back up any accessible data (if possible from the recovery environment) and then perform a clean installation of Windows. Without the BitLocker recovery key, the data on the encrypted drive cannot be accessed and the drive must be formatted before reinstalling.

    This situation is a BitLocker protection and boot corruption issue triggered by the update, not a problem caused by the J: drive letter itself.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.