From: Lee <ler762@gmail.com>
To: cygwin-talk@cygwin.com
Cc: fergus@bonhard.uklinux.net
Subject: Re: Windows cannot update
Date: Sat, 03 Aug 2019 18:25:00 -0000 [thread overview]
Message-ID: <CAD8GWsv+Y_EMY08YfVWsRVWnUdGqJHM+c2TwL+wix4f9w3nEEA@mail.gmail.com> (raw)
In-Reply-To: <20190803162759.7475283.43344.521@bonhard.uklinux.net>
On 8/3/19, Fergus wrote:
> I'm reaching out in desperation to a knowledgeable group. The difficulty is
> not Cygwin related.
> I am using Windows 7 Pro 32-bit. (Yes I know, but with 6 months to go it's
> not completely daft.)
> For 10 days I have been unable to update , getting a "Windows could not
> search for new updates" error message with a 8007000E error code.
A search for "windows error 8007000E" gets this:
https://www.repairwin.com/windows-update-8007000e-error-solved/
Windows Update 8007000E error (SOLVED)
If you receive the Windows Update error code 8007000E while
searching for updates, then probably the Windows update store folder
is corrupted and you have to re-created it.
I don't know what their policy is now, but it used to be that M$
Support calls were free for security issues.. like not being able to
get updates.
Regards,
Lee
> I've been online and tried EVERYTHING from sfc to renaming
> WINDOWS\SoftwareDistribution and off-ing and on-ing key services to
> installing the Update application (didn't know there was one, additional to
> "Control Panel > Windows Update") to endlessly reconfiguring the Windows
> Update settings. I've even re-installed from a Windows 7 Pro SP1 iso, but
> landed in the same place. Windows is activated just fine, it just refuses to
> Update.
> I've had it before and have some kind of recall that it fixed itself when I
> wasn't looking or trying. No such luck currently.
> As stated above, I have other machines with perfectly configured and
> maintained Windows 7 Pro 64-bit, and Windows 10 Pro. But I just want this
> one to work too. Have any of you accomplished savvy tekky people been here
> yourself? Do you know EXACTLY what to do?
> THANK YOU for bothering to read this.
> Fergus
>
next prev parent reply other threads:[~2019-08-03 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9D9AC45310887B40A7245734E850FBE17909193A@FS-MX02.frontier.local>
2019-08-03 16:28 ` Fergus
2019-08-03 18:25 ` Lee [this message]
2019-08-05 9:09 Fergus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD8GWsv+Y_EMY08YfVWsRVWnUdGqJHM+c2TwL+wix4f9w3nEEA@mail.gmail.com \
--to=ler762@gmail.com \
--cc=cygwin-talk@cygwin.com \
--cc=fergus@bonhard.uklinux.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).