Phone Link, etc

Question

Phone Link, etc

Gary Betourne 0

Windows 11 Build 262220.9022, phone link has become unstable and closes. Over the course of 2 hours, the following occurred:

Faulting application name: PhoneExperienceHost.exe, version: 1.26071.158.0, time stamp: 0x6a3e0000. Faulting module name: Microsoft.UI.Xaml.dll, version: 3.2.3.0, time stamp: 0xc8690d1e Exception code: 0xc000027b. Fault offset: 0x00000000003a9c5d
The attempt to locate the Open procedure "OpenLsaPerformanceData" in DLL "C:\Windows\System32\Secur32.dll" for the "Lsa" service failed with Win32 error code
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID Moderator note: PII removed [0x80040154, Class not registered

4.Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID Moderator note: PII removed and Name SW_PROV is [0x80040154, Class not registered

0 comments

2 answers

Your answer

Answer 1

Emma1-N 10,760 Microsoft External Staff Moderator

Welcome Gary Betourne,

Since this is a public forum, we will hide your personal identifiable information, and I have sent that image of yours containing your personal identifiable information in a private message so we can work together to resolve the issue.

I understand how frustrating it can be when Phone Link (PhoneExperienceHost.exe) has become unstable and closes unexpectedly on Windows 11 Build 262220.9022, and that the Event Viewer is showing Phone Link application crashes along with Volume Shadow Copy Service registration errors.

Before proceeding, I would like to narrow down the issue:

Did the issue begin immediately after installing Build 262220.9022 or another recent Windows update?
Does Phone Link close only when opening specific features (Messages, Calls, Photos), or does it close immediately after launch?

In the meantime, you can try these steps below to troubleshoot the issue:

Option 1: Repair and reset Phone Link

Go to Settings > Apps > Installed apps
Find Phone Link
Select Advanced options
Run Repair, then Reset

Option 2: Re-register Phone Link components

Open Windows PowerShell as Administrator
Run: Get-AppxPackage Microsoft.YourPhone -AllUsers | Reset-AppxPackage
Restart the PC

Option 3: Repair Windows system files

Open Command Prompt as Administrator
Run: DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow
Restart after both commands complete

Option 4: Check Windows App SDK Runtime

Go to Settings > Apps > Installed apps
Verify Microsoft Windows App Runtime packages are present
Install any pending Microsoft Store updates

Option 5: Reinstall Phone Link

Uninstall Phone Link
Restart the PC
Reinstall it from Microsoft Store

I hope the steps above help you deal with your issue.

If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Emma1-N 10,760 Reputation points Microsoft External Staff Moderator

2026-08-08T04:10:25.4833333+00:00

Hello Gary Betourne,

I just wanted to check if my previous response addressed your question correctly. If there is anything I may have misunderstood, I would truly appreciate it if you could provide a bit more detail to help me better understand your needs.
Gary Betourne 0 Reputation points

2026-08-08T12:41:17.3866667+00:00

Emma1-N: I appreciate your response, but none of your options could either not be found or did nothing to change the instability of Phone Link for this Evaluation build..9022. I have not determined what action is causing it.
Gary Betourne 0 Reputation points

2026-08-08T13:21:51.13+00:00

Another glitch has appeared now in Phone Link operations for Build 26220.9022. Currently, some notifications can be deleted while others cannot. I haven't made an association.
Gary Betourne 0 Reputation points

2026-08-10T00:11:34.9333333+00:00

This message was triggered dozens of times as I tried to close Windows using the Start Button. "Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID Moderator note: PII removed} and Name SW_PROV is [0x80040154, Class not registered."
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Gary Betourne 0 Reputation points

2026-08-10T12:45:08.92+00:00

Currently, the Phone Link is not the only problem I'm having with this build. I just ran DISM and a few other tools. I'll see if things settle down.
Emma1-N 10,760 Reputation points Microsoft External Staff Moderator

2026-08-11T07:27:04+00:00

Hello Gary Betourne,

Thanks for the update. Hopefully the DISM repairs help stabilize the build. Please let me know if the issues persist.
Gary Betourne 0 Reputation points

2026-08-11T19:09:38.7366667+00:00

After 2 days of working normally, I get this: Faulting application name: PhoneExperienceHost.exe, version: 1.26071.158.0, time stamp: 0x6a3e0000. Faulting module name: Microsoft.UI.Xaml.dll, version: 3.2.3.0, time stamp: 0xc8690d1e. Exception code: 0xc000027b. Fault offset: 0x00000000003a9c5d. Event 1000. AND,

138 events of these over a few minutes alternating between Event 12292 and 22: Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, Class not registered.

].
Emma1-N 10,760 Reputation points Microsoft External Staff Moderator

2026-08-12T07:57:55.1133333+00:00

Hello Gary Betourne,

Thank you for the additional details. With 138 Event ID 1000 PhoneExperienceHost.exe crashes and 22 VSS Event ID 12292 errors (0x80040154 - Class not registered) in only two days, this appears to extend beyond a normal Phone Link application issue.

To help narrow this down, could you confirm whether these VSS errors are still being logged when Phone Link is completely closed, or do they only appear around the time Phone Link crashes?
Gary Betourne 0 Reputation points

2026-08-12T13:51:02.36+00:00

There was a Phone Link update this morning. I loaded the update and cold booted. So far, no problems.
Emma1-N 10,760 Reputation points Microsoft External Staff Moderator

2026-08-13T08:22:50.9233333+00:00

Hello Gary Betourne,

Thank you for your update. If you still have any questions, please let me know. I will be here to assist you
Gary Betourne 0 Reputation points

2026-08-13T12:35:37.8966667+00:00

From a cold boot this morning: "Faulting application name: PhoneExperienceHost.exe, version: 1.26072.246.0, time stamp: 0x6a3e0000

Faulting module name: Microsoft.UI.Xaml.dll, version: 3.2.3.0, time stamp: 0xc8690d1e

Exception code: 0xc000027b

Fault offset: 0x00000000003a9c5d

Faulting process id: 0x1A98

Faulting application start time: 0x1DD2B1F1255585F

Faulting application path: C:\Program Files\WindowsApps\Microsoft.YourPhone_1.26072.246.0_x64__8wekyb3d8bbwe\PhoneExperienceHost.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.2_2.3.1.0_x64__8wekyb3d8bbwe\Microsoft.UI.Xaml.dll

Report Id: 3145cdab-e4dc-4288-a8b8-983bc68f6306

Faulting package full name: Microsoft.YourPhone_1.26072.246.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App"

The fault came as I was looking at the messages and the app just closed.
Emma1-N 10,760 Reputation points Microsoft External Staff Moderator

2026-08-14T08:03:16.98+00:00

Hello Gary Betourne,

To help isolate whether this is specific to your current Windows profile, could you test Phone Link from a newly created local administrator account and let us know if the same crash occurs there?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Gary Betourne 0 Reputation points

2026-08-14T14:33:41.2866667+00:00

Two errors this morning: Faulting application name: YourPhoneAppProxy.exe, version: 1.26072.246.0, time stamp: 0x6a3e0000. Faulting module name: YourPhoneAppProxy.Contract.dll, version: 1.26072.246.0, time stamp: 0xc689695c. Exception code: 0x80131623. Fault offset: 0x00000000000537b1. Faulting process id: 0x3BD8. Faulting application start time: 0x1DD2BF8DC828739. Faulting application path: C:\Program Files\WindowsApps\Microsoft.YourPhone_1.26072.246.0_x64__8wekyb3d8bbwe\YourPhoneAppProxy.exe. Faulting module path: C:\Program files\WindowsApps\Microsoft.YourPhone_1.26072.246.0_x64__8wekyb3d8bbwe\YourPhoneAppProxy.Contract.dll. Report Id: d879ec73-d01f-47e2-acd4-ece28c282011. Faulting package full name: Microsoft.YourPhone_1.26072.246.0_x64__8wekyb3d8bbwe. Faulting package-relative application ID: App

AND:Application: YourPhoneAppProxy.exe. CoreCLR Version: 10.0.1026.32716.NET Version: 10.0.10. Description: The application requested process termination through System.Environment.FailFast.

I was looking at a text that should have contained an image, and Phone app closed abruptly.
Gary Betourne 0 Reputation points

2026-08-14T15:04:34.45+00:00

I cold booted again. These same 2 errors seemed to occur when the Phone Link app opens. However, it runs normally for an undetermined time.
Emma1-N 10,760 Reputation points Microsoft External Staff Moderator

2026-08-15T10:08:02.67+00:00
Hello Gary Betourne,

I sincerely apologize that the steps I suggested were not able to help you resolve the issue.

For faster and more specialized assistance, I kindly recommend reaching out to Live Chat Support. Support agents are available to help you troubleshoot the issue in real time and provide more in‑depth guidance. Please follow the steps below to connect with Live Chat Support.

Visit the Microsoft Support contact page: Contact - Microsoft Support

In the search bar provided on the page, type "Phone link issue" and press Enter.

Click on the "Get Help" button that appears.

Scroll down the page until you see and click on the "Contact Support" option.

When prompted to select your product or service, choose "Other Products".

Look for and click on "Chat with a support agent in your web browser".

When prompted, provide a valid contact email where Microsoft can reach you regarding your case.

Explain your situation clearly: Be concise but provide all the relevant details.

Disclaimer: Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas.
Gary Betourne 0 Reputation points

2026-08-15T11:31:37.27+00:00

New error following the failed attempt to add another user and rebuilding the whole driver system. "Application: YourPhoneAppProxy.exe

CoreCLR Version: 10.0.1026.32716

.NET Version: 10.0.10

Description: The application requested process termination through System.Environment.FailFast.

Message: Task Faulted at File: App.xaml.cs Method: OnStartup Line: 173

Description: The process was terminated due to an unhandled exception.System.TypeLoadException: Could not load type 'System.StubHelpers.InterfaceMarshaler' from assembly 'System.Private.CoreLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e'.

at MS.Win32.UnsafeNativeMethods.TF_CreateInputProcessorProfiles(ITfInputProcessorProfiles& profiles)

at System.Windows.Input.InputProcessorProfiles.Initialize(Object o)

at System.Windows.Input.InputLanguageSource.EnsureInputProcessorProfile()

at System.Windows.Input.InputLanguageManager.add_InputLanguageChanged(InputLanguageEventHandler value)

at YourPhoneAppProxy.Core.Input.KeyboardStateManager..ctor()

at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Constructor(Object obj, IntPtr* args)

at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass2_0.<RealizeService>b__0(ServiceProviderEngineScope scope)

at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(ServiceIdentifier serviceIdentifier, ServiceProviderEngineScope serviceProviderEngineScope)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)

at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)

at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredServiceT

at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)

at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)

at System.Lazy`1.CreateValue()

at YourPhoneAppProxy.Views.AppProxyWindowManager.<SetupWindowIfNeeded>b__22_0()

at System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout)

at System.Windows.Threading.Dispatcher.Invoke(Action callback)

at YourPhoneAppProxy.Views.AppProxyWindowManager.SetupWindowIfNeeded()

at YourPhoneAppProxy.Core.Initialization.Initializers.PreProcessInitializer.OnStartupImplAsync(AppLaunchType launchType, String hostedAppId, String correlationId)

at YourPhoneAppProxy.Core.Initialization.Initializers.InitializerBase.OnStartupAsync(AppLaunchType launchType, String packageId, String hostedAppId, String correlationId, String explicitLaunchSessionId)

at YourPhoneAppProxy.Core.Initialization.AppProxySetupManager.StartupImplAsync(AppLaunchType launchType, String packageId, String hostedAppId, IHealthActivity appProxySessionActivity, Guid constructorToShowGuid, String explicitLaunchSessionId)

at YourPhoneAppProxy.Core.Initialization.AppProxySetupManager.StartupAsync(AppLaunchType launchType, String packageId, String hostedAppId, IHealthActivity appProxySessionActivity, Guid startUpGuid, Guid constructorToShowGuid)

Stack:

at System.Environment.FailFast(System.Runtime.CompilerServices.StackCrawlMarkHandle, System.String, System.Runtime.CompilerServices.ObjectHandleOnStack, System.String)

at System.Environment.FailFast(System.Threading.StackCrawlMark ByRef, System.String, System.Exception, System.String)

at System.Environment.FailFast(System.String, System.Exception)

at YourPhoneAppProxy.Core.Utils.TaskExtensions+<>c__DisplayClass7_0.<HandleTaskContinueWith>b__0(System.Threading.Tasks.Task)

at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef, System.Threading.Thread)

at System.Threading.Tasks.ThreadPoolTaskScheduler.TryExecuteTaskInline(System.Threading.Tasks.Task, Boolean)

at System.Threading.Tasks.TaskScheduler.TryRunInline(System.Threading.Tasks.Task, Boolean)

at System.Threading.Tasks.TaskContinuation.InlineIfPossibleOrElseQueue(System.Threading.Tasks.Task, Boolean)

at System.Threading.Tasks.Task.ContinueWith(System.Action`1<System.Threading.Tasks.Task>, System.Threading.Tasks.TaskScheduler, System.Threading.CancellationToken, System.Threading.Tasks.TaskContinuationOptions)

at YourPhoneAppProxy.Core.Utils.TaskExtensions.HandleTaskContinueWith(System.Threading.Tasks.Task, YourPhoneAppProxy.Telemetry.ITelemetryFactory, YourPhoneAppProxy.Telemetry.IHealthActivity, System.String, System.String, System.String, Int32, Boolean)

at YourPhoneAppProxy.Core.Utils.TaskExtensions.LogAndFailFastOnFaulted(System.Threading.Tasks.Task, YourPhoneAppProxy.Telemetry.ITelemetryFactory, YourPhoneAppProxy.Telemetry.IHealthActivity, System.String, System.String, System.String, Int32)

at YourPhoneAppProxy.App.OnStartup(System.Windows.StartupEventArgs)

at System.Windows.Application.<.ctor>b__1_0(System.Object)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

at System.Windows.Threading.DispatcherOperation.InvokeImpl()

at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)

at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)

at System.Windows.Threading.DispatcherOperation.Invoke()

at System.Windows.Threading.Dispatcher.ProcessQueue()

at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

at System.Windows.Threading.Dispatcher.Invoke(System.Windows.Threading.DispatcherPriority, System.Delegate, System.Object)

at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)

at System.Windows.Application.RunDispatcher(System.Object)

at System.Windows.Application.RunInternal(System.Windows.Window)

at YourPhoneAppProxy.App.Main()"

However, Phone Link is still running.
Gary Betourne 0 Reputation points

2026-08-18T15:03:33.2066667+00:00
Another Windows 11 system update installed this morning (Build 26220.9202) and an update to Phone Link. Unfortunately, the same two failures occurred upon auto opening, but Phone Link (Ver 1.26072.249.0) still seems to be working.

Faulting application name: YourPhoneAppProxy.exe, version: 1.26072.246.0, time stamp: 0x6a3e0000 Faulting module name: YourPhoneAppProxy.Contract.dll, version: 1.26072.246.0, time stamp: 0xc689695c Exception code: 0x80131623. Event 1000.

Application: YourPhoneAppProxy.exe. CoreCLR Version: 10.0.1026.32716. .NET Version: 10.0.10 Description: The application requested process termination through System.Environment.FailFast. Event 1025.
Emma1-N 10,760 Reputation points Microsoft External Staff Moderator

2026-08-19T07:43:31.0766667+00:00

Hello Gary Betourne,

Thank you for the update. Since Phone Link continues to function while the crashes now involve YourPhoneAppProxy.exe and .NET FailFast (Event ID 1025) after updating to Build 26220.9202, this further suggests the issue is tied to the current Insider build rather than a specific Phone Link installation.

Can you confirm whether any Phone Link features (Messages, Calls, Notifications, Photos) stop working after these events, or are the errors only appearing in Event Viewer while the app remains usable?
Gary Betourne 0 Reputation points

2026-08-24T12:08:25+00:00

Post update of Build 26220.9223: The Phone Link "Clear All" or Clear notifications does not work. Selecting "Quit closes Phone Link and removes the icon and preventing a restart. In an unrelated matter, on startup: "An unexpected error was encountered attempting to retrieve the BitLocker volume master key during restart. Event 24641.
Gary Betourne 0 Reputation points

2026-08-24T22:05:23.5333333+00:00

It's back. While adding a comment to text in Phone Link: Faulting application name: PhoneExperienceHost.exe, version: 1.26072.251.0, time stamp: 0x6a630000

Faulting module name: Microsoft.UI.Xaml.dll, version: 3.2.3.0, time stamp: 0x013b7243

Exception code: 0xc000027b

Fault offset: 0x00000000003a9c5d

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more