Anyone else having probs with elements and w10?
 

On Jul 30, 2018, Paul Carmichael wrote
(in article ):

Just went to use Elements 15 on this W10 Pro64 box and it just freezes. So
does version13. Lightroom works just fine.

Anybody else seen this? I used the program a few weeks ago. Tried to restore
to a previous state but the operation fails (no reason given - good old MS).

Have you recently updated Win10?

If so, you might try a full reinstall of PSE 15.

--

Regards,
Savageduck

Anyone else having probs with elements and w10?
 

In article , Paul Carmichael
wrote:

Just went to use Elements 15 on this W10 Pro64 box and it just freezes. So
does version13. Lightroom works just fine.

Anybody else seen this? I used the program a few weeks ago. Tried to
restore to a previous state but the operation fails (no reason given - good
old MS).

Have you recently updated Win10?

If so, you might try a full reinstall of PSE 15.


Completely removed and re-installed. Just as broken. Even the window controls are
unresponsive, so very dead.

since more than one app has issues, the problem is with the operating
system and/or the hardware.

Anyone else having probs with elements and w10?
 

On Jul 30, 2018, Paul Carmichael wrote
(in article ):

On 30/07/18 14:49, Savageduck wrote:
On Jul 30, 2018, Paul Carmichael wrote
(in article ):

Just went to use Elements 15 on this W10 Pro64 box and it just freezes. So
does version13. Lightroom works just fine.

Anybody else seen this? I used the program a few weeks ago. Tried to
restore to a previous state but the operation fails (no reason given - good old MS).

Have you recently updated Win10?

It has automatic updates.

I think I see your problem.

If so, you might try a full reinstall of PSE 15.

Funny how PSE 13 is also borked...

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.

--

Regards,
Savageduck

Anyone else having probs with elements and w10?
 

On 7/30/2018 10:21 AM, Savageduck 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. 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.

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.

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

--
best regards,

Neil

Anyone else having probs with elements and w10?
 

On Jul 30, 2018, Neil wrote
(in article ):

On 7/30/2018 10:21 AM, Savageduck 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. 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.

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.

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

That raises the question; why should developers have to chase their tails if
they have delivered an app, any app, that conforms to current OS specs, only
to have their app functions undermined by a fractional OS update?

That still sounds like a failure on the part of MS. It seems that every Win
update brings fresh issues, from broken printer drivers, to stuff such as
Paul’s PSE 15 issue.

Most developers plan and work on updates for their software in concert with
Beta releases of OS updates/upgrades.

--

Regards,
Savageduck

Anyone else having probs with elements and w10?
 

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.

Anyone else having probs with elements and w10?
 

In article .com,
Savageduck 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. 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.

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.

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

That raises the question; why should developers have to chase their tails if
they have delivered an app, any app, that conforms to current OS specs, only
to have their app functions undermined by a fractional OS update?

because the specs are very complex and in many cases, subject to
interpretation.

That still sounds like a failure on the part of MS. It seems that every Win
update brings fresh issues, from broken printer drivers, to stuff such as
Paul¹s PSE 15 issue.

minor updates generally aren't a problem. it's the major updates that
have issues, such as win10 anniversary update, which broke a ****load
of webcams.

most likely it's windows, but it could be a mix of both. there's no way
to know without looking at crash logs and figuring out exactly what
went wrong.

keep in mind that pse 15 is a couple of years old, which was never
tested on win10 1803, or fcu for that matter.

Most developers plan and work on updates for their software in concert with
Beta releases of OS updates/upgrades.

they do, but there can always be last minute changes, which is why some
developers wait until it's final and released to customers.

Anyone else having probs with elements and w10?
 

On 7/30/2018 3:01 PM, Savageduck wrote:
On Jul 30, 2018, Neil wrote
(in article ):

On 7/30/2018 10:21 AM, Savageduck 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. 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.

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.

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

That raises the question; why should developers have to chase their tails if
they have delivered an app, any app, that conforms to current OS specs, only
to have their app functions undermined by a fractional OS update?

The problem that I described is that the apps *don't* conform to
"current OS specs"... they may RUN on the current OS, but are not
compliant with the published specs. I've seen this kind of problem
created by code that ignores the specs and compilers that were out-of-date.

That still sounds like a failure on the part of MS. It seems that every Win
update brings fresh issues, from broken printer drivers, to stuff such as
Paul’s PSE 15 issue.

It seems to me that PSE is the problem, since both the current and
earlier version 13 failed in (presumably) the same way.

Most developers plan and work on updates for their software in concert with
Beta releases of OS updates/upgrades.

That doesn't mean that they create compliant apps because Beta releases
don't always incorporate all aspects that are in the OS specifications
but the final release does. Developers have to stay "in step" by making
sure their apps are compliant, and while many do, some don't, choosing
not to fix the app until it's broken by a newer OS version. As I see it,
the issue is that it's critical to stay compliant now that Win10
delivers new OS versions frequently and without user interaction.

--
best regards,

Neil

Anyone else having probs with elements and w10?
 

On Jul 31, 2018, Neil wrote
(in article ):

On 7/30/2018 3:01 PM, Savageduck wrote:
On Jul 30, 2018, Neil wrote
(in article ):

On 7/30/2018 10:21 AM, Savageduck 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. 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.

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.

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

That raises the question; why should developers have to chase their tails if
they have delivered an app, any app, that conforms to current OS specs, only
to have their app functions undermined by a fractional OS update?
The problem that I described is that the apps *don't* conform to
"current OS specs"... they may RUN on the current OS, but are not
compliant with the published specs. I've seen this kind of problem
created by code that ignores the specs and compilers that were out-of-date.

That still sounds like a failure on the part of MS. It seems that every Win
update brings fresh issues, from broken printer drivers, to stuff such as
Paul’s PSE 15 issue.
It seems to me that PSE is the problem, since both the current and
earlier version 13 failed in (presumably) the same way.

While Paul might have a responsibility to have PSE updated to match the
current incremental Win10 update, one should consider that it was an
incremental, not a major Win10 update that seems to have broken both editions
of PSE he uses.


Most developers plan and work on updates for their software in concert with
Beta releases of OS updates/upgrades.
That doesn't mean that they create compliant apps because Beta releases
don't always incorporate all aspects that are in the OS specifications
but the final release does. Developers have to stay "in step" by making
sure their apps are compliant, and while many do, some don't, choosing
not to fix the app until it's broken by a newer OS version. As I see it,
the issue is that it's critical to stay compliant now that Win10
delivers new OS versions frequently and without user interaction.

From the perspective of a macOS user it still looks like a uniquely Win10
issue. Fortunately for me Win10 is a non-issue, I have not used Windows of
any vintage since I retired in 2009. That does not mean that I cannot
appreciate Paul’s dilemma.

--

Regards,
Savageduck

Anyone else having probs with elements and w10?
 

In article , Neil
wrote:

That still sounds like a failure on the part of MS. It seems that every Win
update brings fresh issues, from broken printer drivers, to stuff such as
Paul¹s PSE 15 issue.

It seems to me that PSE is the problem, since both the current and
earlier version 13 failed in (presumably) the same way.

or it's a bug in win10 that affects multiple apps that use a feature
which photoshop uses, which microsoft will fix in a future update.