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.
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.
It is a presumption that I would not count on that a spec will only be
implemented in a "major Win10 update". If the current version of PSE
runs on the current OS version, that says all that one needs to know
about where the problem lies.
it says absolutely nothing.
microsoft could have broken something in the update, such as what they
did with anniversary update, and then fix it shortly after:
https://lifehacker.com/windows-10-an...e-millions-of-
webcams-1785545990
The Windows 10 Anniversary Update has reportedly broken millions of
webcams. If your webcam has been affected, therešs a workaround to
get it back if you donšt mind tweaking your registry a bit.
or are you going to claim that millions of webcams were at fault
because before anniversary update, they were working fine?
more recently:
https://answers.microsoft.com/en-us/...-10-windows-in
stall/devices-with-certain-intel-ssds-may-enter-a-uefi/703ab5d8-d93e-432
1-b8cc-c70ce22ce2f1
Devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may
crash and enter a UEFI screen after reboot when upgrading to Windows
10 April 2018 Update
....
Update (6/22/18):
Microsoft has included a solution for this issue in the May 23, 2018
Cumulative Update (KB4100403). This solution prevents the issue from
occurring when installing the April 2018 Update.
are you going to claim that intel ssds, a standard m.2 device, which
were working fine before the update and made by the same company that
makes the processors in most windows pcs (i.e, not some noname chinese
crap), were non-compliant and at fault?
in both cases (and many others), microsoft admitted they ****ed up and
released a fix.
microsoft's track record is not very good.
sometimes (although not as much lately), they intentionally break
things to force users to upgrade.
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.
Isn't the perspective of non-Windows users pretty irrelevant when
addressing these kinds of issues?
absolutely not.
the very same issues apply to all platforms.
I'm speaking from decades of
experience with Windows and all kinds of apps, including some Adobe
apps, that have taught me to look into these issues from a fact-based
perspective that included reading MS' published specs. I still follow
these programming-related matters on a _daily_ basis.
lots of words that say nothing.
you have absolutely no idea what the cause of this particular issue is
and are just guessing.
without crash logs, debugging tools, source code to the relevant parts
and a solid understanding of how it all fits together (none of which
you have), there's no way to know exactly what the cause is.
rarely is it what it first appears to be and many times, not due to one
single cause.
even if a developer follows the specs to the letter, things can still
break. nothing is 100% bug-free.
i remember chris cox talking about how photoshop would crash on certain
pcs while other apps worked fine and people were quick to blame adobe.
it turned out to be buggy drivers and photoshop was the only app to
push things hard enough to cause it to fail.