I just tried it, works fine for me.  I don't have "Old New Explorer" installed, I know a lot of people use it, maybe something involving that? Here's my about wb:

Windows 10 Home (16299.rs3_release.170928-1534)

WindowBlinds 10.65 (048 - Windows 10 Edition) - 64 bit OS

Window titlebar blur features are enabled on this operating system

Wblind.dll                2017/09/05 08:42:33

Wblind64.dll              2017/09/05 08:42:00

Wbsrv.dll                2017/03/28 07:53:46

WB10Config.exe            2017/09/05 08:42:09

Wbload.dll                2017/09/14 14:51:13

Screen10.exe              2017/03/28 07:53:17

Using Win 10 Pro here up to date version. Also have OldNewExplorer installed. Just tried 6 skins. All different ones including the Default one. - No such problem.

Note: For general information. With Win 10 its not called "Windows Explorer" The correct name is "File Explorer"

yea I know, I'm a creature of habit...thnx for pointing it out though  I'm not sure if I installed OldNewExplorer how can I tell? I also noticed that file explorer is the only thing I have issues with Microsoft edge and IE 11 go to full screen no problem. ok so I thought OldNewExplorer was a windowblinds install option so I googled it and installed it now fullscreen works, thnx for the help peeps.

Great. 

oldnewexplorer even skins and shows menus like win 7

NOTE: oldnewexplorer -- In the configuration window. Make sure near the bottom where it says  "Use alternate navigation bottom style" is not checked. If it's checked buttons that you can use are hidden. It's a great little program that adds a little more to the wonderful StarDock products..

How...bizarre.  I only mentioned it because I don't have it installed and don't have a problem, and I thought there might be something quirky happening with it since people do use it.  Very, very strange.

Yes Dave it is. I only mentioned it because you said you didn't use it. Was just pointing out I was using it and had no problems. So that left us using and not using it without a problem. 

Main thing for what ever reason everything is working for him now.

To follow up it's still a bug when one has to use a 3rd party app to keep file explorer from crashing.

I know installing "Old New Explorer" somehow fixed it for you, but as I said earlier I'm not seeing it without "Old New Explorer".  I would be curious to see if the problem remained "fixed" if you now uninstalled "Old New Explorer".  I'm not really saying you should do that, but I myself would just out of sheer curiosity. It seems like something else is at play here.

If you really want Support to look at it, uninstall "Old New Explorer", see if the problem returns, and if it does start up a ticket here:

https://esupport.stardock.com/index.php?/Tickets/Submit

does it matter what skin you are using and what skin are you presently using?

I tried it on a few random skins before I replied Wednesday, couldn't really say which ones.

I just now ran through the shipped skins, toggling the [F11] a half dozen times on each, they work fine for me.  Acrylic 7, Corporate, Diamond, Echo, Eva, Ice, Lantana, Modern, Precision, The Captain, Win8, Win8 Metro.  Do those work for you without Old New Explorer?

Faulting application name: explorer.exe, version: 10.0.16299.98, time stamp: 0x039c9471

Faulting module name: ntdll.dll, version: 10.0.16299.64, time stamp: 0x493793ea

Exception code: 0xc0000409

Fault offset: 0x0000000000090d5f

Faulting process id: 0xe18

Faulting application start time: 0x01d37076465e343a

Faulting application path: C:\Windows\explorer.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: fe38bab1-7480-47d3-9586-15f912129055

Faulting package full name:

Faulting package-relative application ID:

That would be something you would want to send to them.  I  have absolutely no idea.

https://esupport.stardock.com/index.php?/Tickets/Submit

just tried that and same thing happened. how odd. tried it twice, and the second time, the explorer process crashed. Using Dlorek WB skin, but doesn't seem to make any difference. I'm using file explorer.

I reported this bug and they've put it in the que as it's reproducible. I wonder how long till the fix is released and I hope I don't have to buy WB's again.

It happens for me too. No I do not use Old New Explorer either.

Support is aware and is looking into this issue

5 months and still looking into it?