From: Mayayana <mayayana@invalid.nospam>
Subject: Re: Lightroom Classic CC problem
Full headers:
Path: news.netfront.net!goblin2!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: "Mayayana" <mayayana@invalid.nospam>
Newsgroups: rec.photo.digital
Subject: Re: Lightroom Classic CC problem
Date: Tue, 6 Feb 2018 10:48:50 -0500
Organization: A noiseless patient Spider
Lines: 68
Message-ID: <p5cipj$o45$1@dont-email.me>
References: <fe6i7dl6hqtfdrk4jberf3gqd5mj0r4mfi@4ax.com>
Injection-Date: Tue, 6 Feb 2018 15:49:07 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="c9db9f0113c3b36efc120c70a4d647d9";
logging-data="24709"; mail-complaints-to="abuse@eternal-september.org";posting-account="U2FsdGVkX19K9Vzbe5s/P7KYGESjKyhUhGwdHWCz+BU="
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
Cancel-Lock: sha1:XWShr15bZeusHpdvOuw+9Xkv/38=
X-Priority: 3
X-MSMail-Priority: Normal
Print Article
Forward Article
"Eric Stevens"<eric.stevens@sum.co.nz> wrote

|   Adobe Photoshop Lightroom has stopped working.
|
|   A problem caused the program to stop working correctly.
|   Windows will close the program and notify you if a solution is
|   available.
|

   You might find something out if there's a button
for "Details". I have Visual Studio installed, which
also gives me the option to debug the CPU instructions!
But it's rare that you'll learn anything helpful from
all that. Sometimes if it tells you a DLL that crashed
then that might tell you something.

  What you're seeing is just a PR wrapper around
a program crash. The program crashed. Microsoft
is making it look like they've got everything under
control: "Don't worry. We're on it." It used to be that
it just crashed. Now Microsoft design it to make
you think there's an army of people in lab coats
standing by to examine the problem and fix it....
And that's why Win10 *must* be spyware. For
your own good.

   So why did the program crash? Maybe it's an Adobe
bug. Maybe it's an incompatible printer driver. Maybe
it's something seemingly unrelated, like a font mixup
or graphics problem. All you can do is to search and
see if someone has figured it out. (And watch out
for false information. There are a lot of people who
stop getting a rash after drinking a Coke and then
jump to the conclusion that Coke cures rashes.)

  But you also have to remember that you really
shouldn't be trying to do real work on Windows 10.
You're an unpaid beta tester. The system configuration
can be changed at any time, willy nilly, as Microsoft
decides to zap you with their next test version that
corporate customers don't have to put up with.

   That may seem snide, or anti-Win10, or
anti-Microsoft, but it's actually just plain fact.
Win10 is not a stable system. System updates
need to be carefully tested over time for
compatibility. Corporate IT people do that before
rolling out updates to their "fleet". Prior to Win10,
even those tested updates were tested for months
or years *before* the IT people got them. A
Windows version or service pack was
created, tested, released to volunteer beta testers
in version after version.... Only after months or
even years of that was the final version released for
IT people to start their own testing. It no longer
works that way. You're getting largely untested
updates that Microsoft forces down your throat
when the mood hits them.

  With Win10, you're running one of the test machines
without getting paid for your trouble.

  But it is worth searching. You'll find out a lot more
that way then by looking specifically in Adobe forums
or photo newsgroups, especially given that you don't
know where the problem is coming from.