Ticketing system web site and fences 3 with Win 10 Insider program broken

from Stardock Forums

Fences is broken in Windows 10 Home Insider Program

I am in the WIndows 10 Insider program. Currently using Build 14343.rs1_release 160506-1708

Screenshot is attached.
After a period of inactivity (Unknown how long, probably about 2 hours) all fences and the desktop become blank. The predefined fences are still visible, just zero content.

F5, refresh, does nothing.
Rebooting or merely logging out and logging back in will bring all the fences back.

It has been this was since I became a member of the insider program a few months ago.
Video card is a nVidia GeForce 980.
Fences version is 3.01, no updates available.

Also: When I tried to login to your side, the login page gives a pink error box that says CRSF Error and won't let me login. Since it is your own web page generating the error, I think you might want to look into that.

Your CAPTCHA is broken.,

Thanks for your help, I'd hate to have to quit using Fences because of the incompatibility.

Three screenshots showing each of the three problems described here.

  

http://screencast.com/t/ang9MJPkGq

http://screencast.com/t/28DaKshYp

http://screencast.com/t/A4pBNYlNY

 

-= Bruce D. Meyer

fences
21,272 views 6 replies
Reply #1 from WinCustomize Forums Top

Bruce, Insider Preview's are, as you (should) know, Microsoft *beta* versions of Windows. *No company in the world* is going to waste time and resources fixing issues that *may or may not* still be there in the next beta build/official release.

When you signed in for the Microsoft's Windows 10 Insider program you should have known already what you were getting yourself into. :)

Reply #2 from WinCustomize Forums Top

Yes what JcRabbit said and, put another way, the Insider Beta Release is the most likely source of the bugs and whatever Application Software changes might be needed can't be determined until Windows has a final release available.

Star Control: Origins
Reply #3 from Stardock Forums Top

Any word on the other two problems related to no captcha and CSRF ?

Actually any developer with large companies that want their products to work with new MS Updates DOES work with the developer preview, that's what it's for. As you (SHOULD) know.

 

 

Reply #4 from WinCustomize Forums Top

Quoting bdmeyer44, reply 3
Actually any developer with large companies that want their products to work with new MS Updates DOES work with the developer preview, that's what it's for. As you (SHOULD) know.

Really? Are you a developer? Because I am. :)

Insider Previews are NOT for developers, they are for *users* to find - and report to Microsoft - issues in those insider previews of Windows. At most, developers will only begin looking for any potential issues on RTM builds.

Let me give you another real life example: some time ago I got a report that Winstep Xtreme was broken in one of the insider previews. I did exactly nothing. The very next build, the reported issue was no longer an issue.

Had I acted on that report, I would have wasted countless hours tracking down and fixing an issue that only existed in that specific (buggy) build, when I could have been doing productive work instead.

If you want to live on the fast lane, that is your right and your choice. Just remember that every choice has consequences and that you should not blame others for *your* choices.

+1 Loading…
Reply #6 from Stardock Forums Top

We love it when folks use our products on betas and report them to us.  We also have a few VMs and other machines running insider builds.  I will tell you that leaving them running untouched for hours is rarely part of our test plans.