Ah-ah! That seems to be the problem, if you select a PNG file from the Windows Setttings -> Personalization panel.

Ok, added support for PNG wallpapers on the panels in Preferences that displayed the current wallpaper as a background.

Also, when dragging and dropping executable files directly from an Explorer folder (e.g.; iexplore.exe) the name of the shortcut is now automatically set to that executable's description (e.g.; while before the resulting shortcut would be named 'iexplore' now it gets named 'Internet Explorer').

Small touches, I know, but the devil is always in the details.

Not shure when the problem started, but trying to change some mouse over efects I have realised that some of them are not working anymore (heal, explode, magic, flare, wind,water, teleport, burn, fireworks, smoke, fire, energize, swirl, ion storm, ignite, bubbles, and plasma).
Maybe is related to 17.12 beta

Eh?! They seem to be working fine here. What happens if you open the Dock Properties dialog, go to the Effects tab, click on one of the Effets Panel buttons and then click 'Play All'?

Has anyone been having problems with icons to UWP apps in the dock appearing as 'blank document' icons, as I describe better HERE?

Not sure if this is limited to my two Windows 10 Virtual Machines.

Had winstep crash 2 times in beta:
first time was out of the blue, without my interaction with any of the docks/shelf/modules, second one was when i tried to launch something from the shelf.

also have noticed that moudules (clock/cpu meter) get 'stuck' sometimes(animation stops)

first crash info:
Problem Event Name: APPCRASH
Application Name: WorkShelf.exe
Application Version: 17.12.0.1221
Application Timestamp: 5a31c287
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.23889
Fault Module Timestamp: 598d4c81
Exception Code: c0000005
Exception Offset: 00058a5b
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 0fe2
Additional Information 2: 0fe22d0dc2d96d51b2c91285d314adb9
Additional Information 3: b9ce
Additional Information 4: b9ce034d883689a1ab7fe99b34019a0e

second crash info:
Problem signature:
Problem Event Name: APPCRASH
Application Name: WorkShelf.exe
Application Version: 17.12.0.1221
Application Timestamp: 5a31c287
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.23889
Fault Module Timestamp: 598d4c81
Exception Code: c0000005
Exception Offset: 00058a5b
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 0fe2
Additional Information 2: 0fe22d0dc2d96d51b2c91285d314adb9
Additional Information 3: b9ce
Additional Information 4: b9ce034d883689a1ab7fe99b34019a0e

Does it spontaneously resume?



c000005 is the code for Access Violation. Also seems to be in the same spot both times.

Unfortunately that info relates to ntdll.dll. It tells me nothing of where the fault was generated inside WorkShelf.

sometimes spontaneously, sometimes after i interact with winstep


so far it happened only 2 times and i have been hooked to tv all the while (so lots of resolution changes since hotel tv has a mind of its own when it should shut down) so it could be tied to that and not to beta

How isn't anyone complaining about this? It's driving me up a wall...

I managed to reproduce the issue on a non-VM Windows 10 machine here, but what is happening makes absolutely no sense! Seems to be some kind of system image list issue but, at the same time, also something to do with the Shell item IDs (IDL) of the UWP apps.

I happened to have an old MS Edge shortcut in the dock I had dragged there some time ago - that one always displays the proper icon. When comparing the Shell Item IDs of the old and the new (which displays the blank document icon image) MS Edge shortcuts in the dock the IDs are different! However, both IDs (IDLs) were retrieved by parsing the same AppID string via ParseDisplayName so they should be the same - but aren't. Which means Windows 10 is now returning God knows what and whatever it pleases in ParseDisplayName.

Also, sometimes the UWP apps on the dock will display the blank document icon, other times they will display the proper icon. Getting the proper icons also seems to be apparently related to having UWP app shortcuts already on the desktop?! Aaaargh. FML! MS programmers can go burn in hell for all I care - I'm sure there is a very special place in hell reserved just for them.

winstep wrote:



I have tried that. All the effects mentioned in my previous post just do nothing in Effects Panel. They stay still with the demo icons, while the rest swing, bounce or whatever. The only common nominator I could see is the fact that all the icons not working imply some sort of addition to the base icon (sparkles, fire, glow, etc) with only exception being sonic boom ( allthough that one really all it does is zooming the outer part of the base icon so kind of the same thing as the others that work)

winstep wrote:




I do get sometimes the white paper icon. It does not happen to often, when it does I just delete the shortcut and add a new one. I have not managed to find a pattern there.

Looks like you somehow deleted the WsFxImageRes.dll from

C:\Program Files (x86)\Winstep\

It holds the images required for most particle effects.

winstep wrote:



Thank you for pointing me in the right direction. The file was present in the C:\Program Files (x86)\Winstep\ location. Problem was that sometimes I had crashes of the workshelf (most likley becouse of fast start option) so I had to restart that module manualy. I made the mistake of starting that from another folder: C:\Users\Public\Documents\Winstep that showed first at at a shearch in start menu (windows start menu).
Running workshelf.exe from Program Files fixed the problem.

Thank you again for your time!

Is that only since the beta? Have you read Seeker's post above?

winstep wrote:



I did read Seeker`s post above. Actually after the 17.12 beta I did not have the crash problems, but I am quite sure it was related to Enable fast boot option, that is now deactivated. I have suspected that those crashes were related with that for a while now, but I was willing to take it as such, given the fact that the crashes happened only occasionally. That would be the reason I can not reliably test that now. I will leave that setting off for another week, then I`ll set it back to on and then see what will happen.