RPC error when connecting to network shares with authentication in RE version 10.0.2600.1 on Win11 24H2

Question

Hello, since upgrading to 24H2 I am no longer able to connect to network locations in RE version 10.0.2600.1 without getting an RPC error. This was tested on a wired connection.

The error comes up when using authentication; guest accessed network locations do not experience this issue.

To test the problem, I have installed latest Win11 24H2 and latest Win11 23H2 side by side on VMs.

After first time login, I restarted the VMs into their RE environments through Settings > System > Recovery > Advanced Startup > Restart Now.

When loading RE choose the CMD option and load networking:

wpeutil InitializeNetwork

Then attempted to connect to a network location that requires authentication:

net use z: \\serverip\share /user:domain\user

After submitting the above, I was asked to authenticate. Entering the password and pressing Enter resulted in an error:

The remote procedure call failed and did not execute.

At this point you have to restart the environment in order to attempt connecting again.

As mentioned, this problem doesn’t appear when accessing Guest enabled shares. Doing everything that I have mentioned above, but instead trying to net use into a share that has Guest enabled, you will never get asked for a PW, and the env doesn’t produce the same error, you’re able to connect.

Repeating the same steps on RE version 10.0.22621.5039 on 23H2 doesn’t show this problem, the resulting message is:

The command completed successfully.

Taking this test to HW, I have also noticed is that Wireless SSIDs configured with WPA2 and 3 are no longer visible in this RE version, I can only see SSIDs configured with WPA1.

I have done some further troubleshooting and have found that if you stop lanmanworkstation service in RE version 10.0.2600.1, you cant start it back up again and have to reboot the env to get it into a working state.

Error:

[SC] StartService FAILED 1069:
The service did not start due to a logon failure.

The way I have done this was:

X:\Windows\System32>C:
C:\>CD Windows\System32
C:\Windows\System32>sc query lanmanworkstation
SERVICE_NAME: lanmanworkstation
        TYPE               : 20  WIN32_SHARE_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\Windows\System32>sc stop lanmanworkstation
SERVICE_NAME: lanmanworkstation
        TYPE               : 20  WIN32_SHARE_PROCESS
        STATE              : 3  STOP_PENDING
                                (STOPPABLE, PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x1
        WAIT_HINT          : 0x15f90
C:\Windows\System32>sc query lanmanworkstation
SERVICE_NAME: lanmanworkstation
        TYPE               : 20  WIN32_SHARE_PROCESS
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\Windows\System32>sc start lanmanworkstation
[SC] StartService FAILED 1069:
The service did not start due to a logon failure.

RE version 10.0.22621.5039 on 23H2 doesn’t have these issues, I can see all of my Wireless SSIDs and have no issue restarting the lanmanworkstation service or connecting to password protected network shares.

I use WinRE as a backend for a backup/restore application, and currently I am unable to connect to my backup repositories because of the issues described above. This issue has been ongoing since upgrading to 24H2.

I am hoping that this would get the attention it needs and can be fixed ASAP.

I am aware that I could use WinPE as a work around, but that doesnt resolve the issues I have listed in RE.

I can provide more info on this on request. Thanks in advance!

Answer 1

The same happend to me. The last 24H2 version that worked is from january. From there on, all the RE versions have this problem. Also, there is a post on Veeam Community about this.

https://community.veeam.com/discussion-boards-66/veeam-bootable-media-cannot-connect-to-backup-server-9991?postid=75788#post75788