==== Winhance Log - 2025-02-21 10:17:23 ====
Version: 25.02.17
User: barba
Computer: BK-PC-HP
Elevated Admin: True
PowerShell Version: 5.1.22621.4391

[10:17:23] [INFO] Script started
[10:17:23] [ERROR] Error during application startup: The property 'Name' cannot be found on this object. Verify that the property exists and can be set.
[10:17:23] [ERROR] Error Details:
[10:17:23] [ERROR] Exception Type: System.Management.Automation.RuntimeException
[10:17:23] [ERROR] Stack Trace: at Initialize-InstallationHandlers, : line 3534
[10:17:23] [ERROR] at , : line 9747
[10:17:23] [ERROR] at , : line 1

I've implemented a possible fix for this issue.
Please run my forked version of Winhance to test ?
irm "https://github.com/Nigel1992/Winhance/raw/refs/heads/propertyname-fix-%40-22/2/2025/Winhance.ps1" | iex

Thanks for your response. Still not working but different property.

Can you provide your new log please ?
I need that to figure out what line is giving this error.

Can you provide your new log please ? I need that to figure out what line is giving this error.

Sure, sorry for the late reply. Here is the new log with your forked version.

Winhance-Log_20250227-164832.log

Hi @barbaroskucuk,

I've created a fix for the UI initialization issues you reported. The changes address:

• ShowDialog width error
• CustomizeScreen not found error
• Name property error in installation handlers
• Added proper error handling and logging
• Improved cross-version Windows compatibility

The changes are now in a dedicated branch: fix/initialization-ui-loading-20240227-barbaroskucuk

To test this fix, you can run either of these commands:

Standard Run:

irm "https://raw.githubusercontent.com/Nigel1992/Winhance/fix/initialization-ui-loading-20240227-barbaroskucuk/Winhance.ps1" | iex

Run as Administrator (Recommended):

Start-Process powershell -ArgumentList '-NoProfile -ExecutionPolicy Bypass -Command "irm \"https://raw.githubusercontent.com/Nigel1992/Winhance/fix/initialization-ui-loading-20240227-barbaroskucuk/Winhance.ps1\" | iex"' -Verb RunAs

Please test and let me know if these changes resolve the issues you were experiencing. I've focused particularly on making the initialization more robust across different Windows versions.

Looking forward to your feedback!

@Nigel1992 It is working beautifully. Thank you so much, I really appreciate it.