Hi Christian,

Since Windows 8 you can have a taskbar on every monitor, and decide which items appear on every taskbar (e.g. all items on all taskbars, or only items of windows from the same monitor).

See the image below, or visit this link for a detailed guide.

Relevant topic:

https://tweaker.userecho.com/topics/110-order-lost-when-updating

How can I move that icon from the 3rd line to the 1st line?

You can try the multipage_wheel_scroll advanced option.

Then, you can hold+scroll+release to drag items between pages.

Unfortunately, that doesn't work with a vertical taskbar as far as I remember.

Also, is there a way to force a new icon to go onto the 1st line instead of onto the 3rd line?

7+ Taskbar Tweaker doesn't provide an option that allows that.

From the report I can see that the crash triggers while trying to display a jump list. I'm willing to fix it eventually, but it's not high priority since it's an insider build issue.

Thank you for the report.

I don't see the detection on my computer, and it's not detected by Microsoft on VirusTotal.

There can be several reasons for the detection you see:

• One is that this is a false positive detection. False positives are unfortunately common for new versions of 7+ Taskbar Tweaker. Please see the FAQ here and this blog post.
• The other is that your file is indeed infected. This can happen if you downloaded it on a third party website, or if another malware on your computer infected it. I highly doubt that this is the case, since 5.8 is a relatively new version, and false positives are so common for it.

In any case, if you have any doubt, you can contact Microsoft about it and assure that the file you posses is clean. I guarantee that the files that are served from the official 7+ Taskbar Tweaker website are 100% virus free.

Thank you for the suggestion. Closing since it's a duplicate of this topic:

https://tweaker.userecho.com/topics/608-add-delay-before-decombine-on-hover

Fixed in 7+ Taskbar Tweaker v5.8.

Should be fixed for Windows 10 versions 1803, 1809 and 1909 in the latest beta version, 5.7.1.3.

Should be fixed in v5.7.1.3 beta, please try it.

You can get the beta version here.