Windows 10? Really? A new OS, untested and people want to start using it right away. I would suggest to them to wait until Windows 10 appears on the support platform matrix

Tend to agree with BigLouie. I've never been one for having my clients jump on the new stuff immediately either.

That being said, I have forced myself to try it out earlier than I recommend to my clients just so I can keep a step ahead. Believe me, that was tough when Windows 8 came out. Finally got comfortable with that and now Windows 10? Hope it is an easier transition.

Would be nice to know when Windows 10 compatibility will be available.

Thanks, all for replying.

Have you run Paperless on it?

At Sage Summit, I believe they indicated official Windows 10 compatibility for late October, early November. I'm not absolutely positive, but that is what I recall.

Windows 10 was released just four days ago (July 31, 2015).

Typically Sage 100 tests a new OS for at least 6 months before adding to the supported platform matrix.

Windows 10 may be on a faster track but it is not supported officially right now.

We have moved about five workstations that run MAS 100 to Windows 10 without any issues of significance. However, one of them seems to have slightly degraded resolution in the MAS screens even though all other programs have impeccable quality. I can only think that MAS uses some slightly different video mode that this particular machine's combination of video card and monitor doesn't favor. It's still perfectly usable but the text appears slighly fuzzy.

Are you running paperless on it without issue?

We are running paperless with no issues. There are some sporadic issues with DNS that makes us lose connectivity from time to time but I'm not yet fully convinced this is a Windows 10 issue. We're holding back the rest of the workstations to Windows 7 just to go through a few patch cycles but I have to say, as a user of one of the updated machines, that I like Windows 10. The single most annoying problem is that desktop icons do not remain in position on some machines when rebooted. It's surely something that crept in from using an "update install" rather than a "fresh install".