In article , Neil
wrote:


If the Win10 update has screwed with PSE 15, the same issue with PSE 13
would
not be unusual. Naturally MS will probably admit no fault, and expect Adobe
to come up with a fix for their screw up. Then they will screw up something
else with their next update.

I think your analysis misses a major issue that has existed with apps
since Windows 3.0. It is not at all uncommon for app developers to
disregard MS specifications, even for Adobe apps.

that's true, and app developers who don't use official apis and best
practices have only themselves to blame for any problems.

unfortunately, there are a lot of such developers, however, adobe is
not one of them.

adobe goes well out of their way to only use official apis, even going
so far to work directly with microsoft and apple so that either or both
make the necessary changes to the os so that adobe's apps to continue
to be compliant.

The result is that
while an app may run on the current version of Windows, the next
upgrade/update would cause it to become unreliable or fail completely.

generally that happens with a major update, not an incremental update
as is the case here.

another factor are third party drivers, which are not written by
microsoft or adobe. many of them can be (and often are) very buggy.

Another issue, though not relevant to this situation, is that some users
who don't understand the changes that a newer Windows OS introduces try
to run older apps on the newer OS and experience problems or failures.

again, that depends on many factors.

in general, apps that are well written and use official apis continue
to work, sometimes for many, many years and os revisions, while apps
that rely on undocumented behaviour tend to break, often very quickly.

In either case, the problems are not caused by MS, but by those
disregarding published requirements for the OS.

not necessarily, and without extensive analysis, there's no way to know
exactly what the problem is.