Error notice

[ThreeLlamasInATrenchCoat]

Microsoft PowerToys version

87.1

Installation method

Microsoft Store

Running as admin

None

Area(s) with issue?

PowerToys Run

Steps to reproduce

Error on startup. Maybe related to themes (looking at the error code)...

Version: 0.87.1.0
OS Version: Microsoft Windows NT 10.0.26100.0
IntPtr Length: 8
x64: True
Date: 20-Jan-25 14:50:56
Exception:
System.Windows.Markup.XamlParseException: Set property 'System.Windows.ResourceDictionary.DeferrableContent' threw an exception.
---> System.ArgumentException: Item has already been added. Key in dictionary: 'SystemColorWindowColorBrush' Key being added: 'SystemColorWindowColorBrush'
at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
at System.Windows.ResourceDictionary.SetKeys(IList`1 keyCollection, IServiceProvider serviceProvider)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(Object inst, XamlMember property, Object value)
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
at MS.Internal.AppModel.AppModelKnownContentFactory.BamlConverterCore(Stream stream, Uri baseUri, Boolean canUseTopLevelBrowser, Boolean sandboxExternalContent, Boolean allowAsync, Boolean isJournalNavigation, XamlReader& asyncObjectConverter, Boolean isUnsafe)
at MS.Internal.AppModel.MimeObjectFactory.GetObjectAndCloseStreamCore(Stream s, ContentType contentType, Uri baseUri, Boolean canUseTopLevelBrowser, Boolean sandboxExternalContent, Boolean allowAsync, Boolean isJournalNavigation, XamlReader& asyncObjectConverter, Boolean isUnsafe)
at System.Windows.ResourceDictionary.set_Source(Uri value)
at System.Windows.ThemeManager.GetThemeDictionary(ThemeMode themeMode)
at System.Windows.ThemeManager.ApplyFluentOnWindow(Window window)
at System.Windows.ThemeManager.OnWindowThemeChanged(Window window, ThemeMode oldThemeMode, ThemeMode newThemeMode)
at System.Windows.Window.CreateSourceWindow(Boolean duringShow)
at System.Windows.Window.ShowHelper(Object booleanBox)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Other Software

No response

[similar-issues-ai]

We've found some similar issues:

• C:\Users\ITGurl\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs\0.87.0.0\2024-12-19.txt #36448 , similarity score: 88%
• Error on starting PowerToys #36970 , similarity score: 87%
• something went wrong #36402 , similarity score: 87%
• Power Toys ran into an error #36547 , similarity score: 86%
• PowerToys Run ran into an issue #36658 , similarity score: 86%
• [Run] XamlParseException: Set property 'System.Windows.ResourceDictionary.DeferrableContent' threw an exception #36389 , similarity score: 86%
• PowerToys Run indicates a problem #36557 , similarity score: 86%
• Something went wrong #36821 , similarity score: 83%
• Something went wrong #36896 , similarity score: 82%
• "something went wrong" notyfication. Below detailed logs #36838 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[crutkas]

/dup #36389

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!