sdRohan sdRohan

Start11 1.44 Release Feedback Thread

Start11 1.44 Release Feedback Thread

With the Start11 1.44 release, we are creating this thread so that users can report any observed issues.  

Obtaining the product

Object Desktop members can get the release from within Object Desktop Manager 

Individual purchases (as well as Object Desktop Members) can also be obtained from your account page: https://store.stardock.com/myaccount/products

For guest check-out purchase (no account), from this link: http://www.stardock.com/support/productkeyretrieval

Reporting an issue

Please include the following for anything found:

  • Exact Windows version \ build (winver.exe)

  • Detailed steps to recreate the issue seen

  • Screenshots and videos are very helpful.  Videos can be uploaded to a cloud drive service (GoogleDrive, DropBox, OneDrive, YouTube), with a shared link included in your post.  Images can be copied and pasted directly into a post.

  • If there are specific apps that the app does not work (well) with, please note what apps and their exact versions.  If any app is not common, a link to a trial version would be appreciated.

Thank you for your interest and any time you put into making Start11 a better product.

Sean Drohan
Stardock Support Manager

116,239 views 76 replies
Reply #26 Top

I am having an issue with missing system tray icons when starting up or rebooting. Less than half the icons appear. It doesn't happen consistently - maybe once every 3-4 boots/restarts. This issue seems to come and go depending on the version, but both 1.43 and 1.44 definitely have it. For me, the last version without the issue was Start11_1.4.2.0-j301.

 

System info:

Three monitors: primary is 2560x1440 @ 144Hz. Two and three are 2560x1440 @ 60Hz and 1280x720 @ 60Hz. (The latter one is used for displaying an AIDA64 sensor panel.)

############################
# From msinfo
############################

OS Name Microsoft Windows 11 Pro
Version 10.0.22621 Build 22621
BIOS Mode UEFI
Hardware Abstraction Layer Version = "10.0.22621.1413"
Processor AMD Ryzen 9 3900X 12-Core Processor, 3801 Mhz, 12 Core(s), 24 Logical Processor(s)
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product ROG CROSSHAIR VIII HERO (WI-FI)
BIOS Version/Date American Megatrends Inc. 4402, 2/3/2023
SMBIOS Version 3.3
Embedded Controller Version 255.255
Virtualization-based security Running
Virtualization-based security Required Security Properties
Virtualization-based security Available Security Properties Base Virtualization Support, Secure Boot, DMA Protection, UEFI Code Readonly, Mode Based Execution Control
Virtualization-based security Services Configured Hypervisor enforced Code Integrity
Virtualization-based security Services Running Credential Guard, Hypervisor enforced Code Integrity
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Name Virtual Desktop Monitor
Driver Version 15.39.56.845
INF File oem94.inf (MyDevice_Install.NT section)
Driver C:\WINDOWS\SYSTEM32\DRIVERS\WUDFRD.SYS (10.0.22621.1485, 344.00 KB (352,256 bytes), 4/16/2023 8:12 PM)
Name NVIDIA GeForce RTX 2080 SUPER
PNP Device ID PCI\VEN_10DE&DEV_1E81&SUBSYS_32893842&REV_A1\4&2AE1B128&0&0019
Adapter Type NVIDIA GeForce RTX 2080 SUPER, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 2080 SUPER
Adapter RAM (1,048,576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_e34a87a86b660c23\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_e34a87a86b660c23\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_e34a87a86b660c23\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_e34a87a86b660c23\nvldumdx.dll
Driver Version 31.0.15.3179
INF File oem4.inf (Section001 section)
Color Table Entries 4294967296
Resolution 2560 x 1440 x 143 hertz
Bits/Pixel 32
Memory Address 0xFB000000-0xFC0FFFFF
Memory Address 0xD0000000-0xE20FFFFF
Memory Address 0xE0000000-0xE1FFFFFF
I/O Port 0x0000F000-0x0000FFFF
IRQ Channel IRQ 54
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPIG.INF_AMD64_E34A87A86B660C23\NVLDDMKM.SYS (31.0.15.3179, 55.55 MB (58,251,232 bytes), 5/10/2023 8:19 AM)

############################
# From Nvidia control panel
############################

NVIDIA System Information report created on: 05/10/2023 08:48:28

[Display]
Operating System: Windows 10 Pro, 64-bit
DirectX version: 12.0 
GPU processor: NVIDIA GeForce RTX 2080 SUPER
Driver version: 531.79
Driver Type: DCH
Direct3D feature level: 12_1
CUDA Cores: 3072 
Core clock: 1845 MHz 
Memory data rate: 15.50 Gbps
Memory interface: 256-bit 
Memory bandwidth: 496.06 GB/s
Total available graphics memory: 32722 MB
Dedicated video memory: 8192 MB GDDR6
System video memory: 0 MB
Shared system memory: 24530 MB
Video BIOS version: 90.04.7A.00.9D
IRQ: Not used
Bus: PCI Express x16 Gen3
Device Id: 10DE 1E81 32893842
Part Number: G180 0042

 

Reply #27 Top

Quoting TPScroggins, reply 24


Quoting Don8158,

same problem as before - Taskbar not updating

Edition Windows 11 Pro Version 22H2 OS build 22621.1555

Windows Feature Experience Pack 1000.22640.1000.0



Must reload Explorer to fix.

 



Are you running any other Windows modification software?

Paul Scroggins
Associate Technical Support Analyst

End of TPScroggins's quote
 

Not that I can think of.  

Reply #29 Top

Request for larger buttons (the ones marked in yellow) to make them look like the red ones, as italian translation for "settings" is quite longer:

Thanks!

 

Baio

Reply #30 Top

@Neil Banfield

Quoting Neil, reply 19


Quoting Kouji_Iida,

OS : Windows 11 Pro 22H2
Ver : 1.43 --> 1.44 

Taskbar color and transparency are not working on both sides as below.



Please uninstall Start11 and REBOOT (very important).

Then reinstall Start11 as it looks like your version has not been correctly installed.

End of Neil's quote


Thanks a lot!! It disappeared and never happen again.

Reply #31 Top

Hello,

i found that the Taskbar has an extended layer on top of it self:

(the grey line ontop of the orange line, my Desktop is Black)

 

This Problem was seen firstly when the Windows 11 Searchbar was introduced. With Version 1.42 (i think) it was gone.... until now.

This appears on every Monitor, no matter the Resolution or DPI Scaling.

With the enhanced Taskbar it is removed, but i cant use this because i am using 4 Monitors and dont want the Start button to be aligned left.

 

Winows 11 22H2 (OS build 22621.1702)

Reply #32 Top

Quoting Plll6DiabloPower, reply 31

Hello,

i found that the Taskbar has an extended layer on top of it self:

(the grey line ontop of the orange line, my Desktop is Black)



 

This Problem was seen firstly when the Windows 11 Searchbar was introduced. With Version 1.42 (i think) it was gone.... until now.

This appears on every Monitor, no matter the Resolution or DPI Scaling.

With the enhanced Taskbar it is removed, but i cant use this because i am using 4 Monitors and dont want the Start button to be aligned left.

 

Winows 11 22H2 (OS build 22621.1702)
End of Plll6DiabloPower's quote

Uninstall Start11, REBOOT, reinstall Start11 1.44.

Is that better?

Reply #33 Top

short Answer: Nope!

Still the exact same problem. :(

Reply #34 Top

Quoting Plll6DiabloPower, reply 33

short Answer: Nope!

Still the exact same problem. :(
End of Plll6DiabloPower's quote

What are you using to add those red bits to the right end of your taskbar?

Also is this a desktop, laptop or touch based device?

Reply #35 Top

The red bits are just a Bitmap used with the "Use custom taskbar background texture" Feature of Start11. (and yes it is big enough and set to strech)

The Computer is a Dell Inspiron 7706 2in1 Convertible with a Touchscreen (2k native resolution), the externals are 2x 1080p 32" LED Screens and 1x 4k 58" LED Screen.

The Problem occurs with and without the externals connected, no matter the resolution or DPI settings.

Reply #36 Top

Pressing the Windows keys (left and right) no longer brings up the Start11 menu, it brings up the default Start menu instead.

The key sequence Control+Esc also brings up the default Start.

Clicking on the onscreen Start button still does call up the Start 11 menu.

My configuration:

Windows 11 22H2 (OS Build 22621.1776) - Release Preview Channel

This new behavior began to occur after I rebooted my machine on 5/13. Previous reboot was on 5/9.  Between 5/9 and 5/13, these system updates were installed (excluding all the Defender definition updates):

  • Update Stack Package - (Version 1023.421.6122.0)
  • 2023-05 Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5026446)
  • 2023-04 Update for Windows 11 Version 22H2 for x64-based Systems (KB4023057)
  • 2023-05 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5026372)
  • Windows configuration update
  • Windows Malicious Software Removal Tool x64 - v5.113 (KB890830)

No application updates or new installs of any sort occurred in that same period.

 

Edited: Control+Esc behavior

Reply #37 Top

Quoting NoelAng, reply 36

Pressing the Windows keys (left and right) no longer brings up the Start11 menu, it brings up the default Start menu instead.

The key sequence Control+Esc also brings up the default Start.

Clicking on the onscreen Start button still does call up the Start 11 menu.

My configuration:



Windows 11 22H2 (OS Build 22621.1776) - Release Preview Channel

This new behavior began to occur after I rebooted my machine on 5/13. Previous reboot was on 5/9.  Between 5/9 and 5/13, these system updates were installed (excluding all the Defender definition updates):

 

    • Update Stack Package - (Version 1023.421.6122.0)

 

    • 2023-05 Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5026446)

 

    • 2023-04 Update for Windows 11 Version 22H2 for x64-based Systems (KB4023057)

 

    • 2023-05 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5026372)

 

 

    • Windows Malicious Software Removal Tool x64 - v5.113 (KB890830)

 


No application updates or new installs of any sort occurred in that same period.

 

Edited: Control+Esc behavior

End of NoelAng's quote

This will probably be caused by the use of that prerelease version of Windows.

We shall investigate it.

Reply #38 Top

sorry replied accidentally to wrong thread

 

Quoting Neil, reply 34


Quoting Plll6DiabloPower,

short Answer: Nope!

Still the exact same problem. :(



What are you using to add those red bits to the right end of your taskbar?

Also is this a desktop, laptop or touch based device?

End of Neil's quote

Reply #40 Top

I would like to go back to 1.4.3 in the meantime. Is there a way I can still get the installer for 1.4.3?

Reply #41 Top

Quoting claudiu111, reply 40

I would like to go back to 1.4.3 in the meantime. Is there a way I can still get the installer for 1.4.3?
End of claudiu111's quote

The only changes from 1.4.3 to 1.4.4 are as follows:

Start11 1.44 Changelog

05/01/2023

Stardock release: 05/01/2023

Steam: TBD

04/17/2023

  • Tweaked detection of touch mode taskbar enabled devices (should fix misaligned systray issues)

  • Tweaked color of flashing taskbar button in dark more to be more visible

  • Version is 1.44 (1.4.4.0 on file version)

There doesn't appear to be any significant change that would affect your installation.

Reply #42 Top

And somehow there is. Please check my previous post. I tried uninstalling, rebooting reinstalling and I still have that issue.

Reply #43 Top

Quoting claudiu111, reply 42

And somehow there is. Please check my previous post. I tried uninstalling, rebooting reinstalling and I still have that issue.
End of claudiu111's quote

Try running DISM. Here are two links to articles on how to run DISM on Windows 10 and Windows 11.

Windows 10

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

Windows 11

https://www.windowscentral.com/software-apps/windows-11/how-to-use-dism-to-repair-local-image-on-windows-11

Try one of these and see if it resolves your issue.

Reply #44 Top

I ran DSIM, also SFC. My Windows build is fine. And this issue is happening on 2 machines. There is nothing wrong with the OS and I do not use other utilities like Start11 to change the UI.

It would be great if I could get back to 1.4.3 for the moment as I am tired of restarting explorer each time I wake up my computer. As I mentioned before this is happening only after I wake up the computer from sleep. It's fine if I reboot the OS.

Reply #45 Top

Quoting claudiu111, reply 14

Since I installed 1.44 an old issue came back. When my pc wakes up from sleep sometimes the taskbar icons are misaligned. This did not happen on 1.43.

I have small taskbar selected. Running latest Windows 11 build 22621.1635
End of claudiu111's quote

I ran some tests on my Windows 11 test machine. I'm running 25357.1 Canary insider build and Start11 1.44.

This is a Touch screen device, but I have "optimize taskbar for touch..." turned off in the settings.

I set Start11 to enhance the taskbar and selected Never, and set taskbar size to small. Allowed it to go to sleep multiple times and everything looks good. This is on a Surface Pro 4 set to 200% (Recommended) scaling. If I then change the scaling to 100% everything looks good. I then let it go to sleep multiple times and everything still looks good, but then when I change the scaling back to 200%, everything gets wonky with misaligned icons in the taskbar. If I now restart explorer, everything looks good again. Now I let it go to sleep multiple times, and everything still looks good.

This issue definitely has something to do with changing the scaling of the device. I had the same experience as satrafton in replies #20 and 22.

Reply #46 Top

My dpi is at 100% running 1920x1080 res. I do have a 4k TV connected, even though I only use my primary monitor and don't project to the TV, it may affect this in someway but still, it worked fine on 1.4.3 same setup, same settings, same everything.

And I also noticed another strange thing. If I put the computer to sleep, wait 10 seconds and wake it up again this issue does not happen. If it sleeps for a few minutes or more, I get this issue. Perhaps it takes the OS some time to enter proper sleep idk.

Ever since Microsoft made changes to the UI and Stardock had to adapt to that, when the OS starts(normal boot not waking up for sleep), at first the taskbar is large and then it reverts to small and everything gets arranged properly. Start11's service probably kicks in and does its thing. I'm thinking that after waking up from sleep this service might not work properly. Just a thought.

Reply #47 Top

Reporting that the taskbar alignment issue has returned. Occurred after connecting second monitor.

 

Edition Windows 11 Pro

Version 22H2

Installed on ‎11/‎1/‎2022

OS build 22621.1702

Experience Windows Feature Experience Pack 1000.22641.1000.0

RTX 3050 laptop graphic card

Start11 1.44

Taskbars on Top and displayed for both laptop and external monitor.

Issue occurs only on external monitor. Laptop monitor looks fine.

Buttons are set to never combined and appear correctly.

With explorer restart issue is corrected.

 

Reply #48 Top

Quoting acuervofm, reply 47

Reporting that the taskbar alignment issue has returned. Occurred after connecting second monitor.





 

Edition Windows 11 Pro

Version 22H2

Installed on ‎11/‎1/‎2022

OS build 22621.1702

Experience Windows Feature Experience Pack 1000.22641.1000.0

RTX 3050 laptop graphic card

Start11 1.44

Taskbars on Top and displayed for both laptop and external monitor.

Issue occurs only on external monitor. Laptop monitor looks fine.

Buttons are set to never combined and appear correctly.

With explorer restart issue is corrected.

 

End of acuervofm's quote

Which monitor is set to be primary?

Reply #49 Top

All,

Start11 1.45 beta was released today.

https://forums.stardock.com/518875/start11-145-beta-feedback-thread

As always, thanks for your feedback and support.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #50 Top

I am now back at Version 1.41 and this resolves my Problem for the moment (by the way, the new Beta did not)

 

EDITED