Solved Error code 0x8000ffff when Windows 7 Update restarts

[sinned]

Early in February I started getting an error when restarting after a Windows 7 update. I reloaded Windows 7 three different times, then decided that Einstein was right. So, following instructions on this forum, after my 4th restart I got SURT and ran it [see CBS.zip attached], then downloaded Driver Mender & updated my drivers, then started downloading the oldest W7 updates, pre-2013, a clutch at a time, and other software like MS Office a bit at a time, until I had established several good restore points. When I tried to upload the five recommended updates shown in this screenshot,

View attachment 256235

I got the following error message:

View attachment 256236

After choosing Startup Repair, I got this message:

View attachment 256237

After picking a restore point, I got this message:

View attachment 256238

It returned a failure message, thus [the dread error of my title]:

View attachment 256239

So, of course, the system then re-started and reported success, thus:

View attachment 256240

Am I doing something wrong? Is there a bad update out there for an HP laptop as old as mine? Or is this just the effects of too much ice-cream eaten late at night?

 

[mjf]

One piece of advice I found floating around when I received this error was to run a system file check:
from an elevated command prompt
sfc /scannow
In my case I had no system file problems. Since the error didn't reoccur I ignored it.

Regarding "Startup Repair" I have been left in the same state as you indicate in your pics. You may find that you need to run the startup repair multiple times with a reboot in between for it to do its job.
It also isn't a fool proof fixit all solution and you should always have a couple of good system images to fall back on.

 

[NoelDP]

There are no errors in CheckSUR - and nothing in the bare SFC log
However, the CBS logs make interesting reading!
One of the more interesting things is that the data appears to be old - the latest timestamp in the logs is 18th Feb

Please check your system clock/date, and run another SFC /SCANNOW, and post the new CBS.log file

 

[sinned]

Thanks, NoelDP and mjf. I appreciate your help.

I checked my system date and time, and they are correct. The data were old because I first consulted this forum on the 18th, but I didn't have a stable system until last night.

So attached is the new CBS zip file. What was it, NoelDP, that you found interesting in the original?

And, mjf, you say "you should always have a couple of good system images to fall back on." What is a good, reliable software package for creating such system images?

 

[NoelDP]

The most likely solution is going to be a repair of the .NET 4.0 framework.

Open Control Panel, then Programs & Features
In the programs listing, look for the .NET 4.0 Framework (or similar) entry and highlight it.
in the header bar, click on Uninstall/Change
You should be offered the option to Repair the current installation - use that.

When it's complete, reboot TWICE - waiting at least 15 minutes between boots.

then go to Windows Update, and do a manual check for Updates.
Install ONLY ONE of the updates - the oldest, (check the date in the right margin, or in the details)

see if it works OK.

Post back with details.

 

[mjf]

And, mjf, you say "you should always have a couple of good system images to fall back on." What is a good, reliable software package for creating such system images?

I use Windows inbuilt System Imaging and (free) Macrium Reflect.
Although neither have failed me, I think there is a higher Preference for the Macrium Product. A good tutorial download info...
http://www.sevenforums.com/tutorials/73828-imaging-free-macrium.html

 

[sinned]

repair of the .NET 4.0 framework

Thanks, Noel: I undertook the repair, as you specified. First, when I opened up control panel, I found something called "Ms .NET Framework 4 Client Profile," which looked like this:

View attachment 256353

So I proceeded, even though it wasn't the ".NET 4.0 Framework" file you specified, because it was the closest match. I initiated the repair, with a screen that looked like this after a bit:

View attachment 256354

When I rebooted the second time, and opened Windows Update, I found that the oldest update file was this one:

View attachment 256355

So I upgraded to that one, and the machine did not go into its Startup Repair mode.

But that recalled to me what was probably the onset of this problem: Firefox started crashing every time I closed a tab. It would offer to restart, and when I approved that, I could close the tab that had crashed it. But when I closed a different, other tab, it would crash again. Could a corrupted .NET framework cause that problem?

 

[Layback Bear]

You sure need a lot of updates. Do you have SP-1 installed?

 

[NoelDP]

I note that all the updates listed are Optional ones - none are security-related.
You can take the option not to install any of them

 

[sinned]

Service Pack and upgrades

Hi, Noel. One reason I have so many optional updates is that I have not installed most of them. And, Layback, Service Pack 1 was one of the first things that I upgraded to when I re-loaded Windows 7. But I noticed that the System pane in the Control Panel prompts me with a hyperlink to "Get more features with a new edition of Windows 7." What does that mean? Is there a "new edition" or just a Service Pack 2? Since this involves a purchase, I'm a little leery of even looking. Besides, I'm running Windows 7 Home Premium, so wouldn't Professional be next -- and I'm not doing much more than writing, and browsing the web.

Also, do any of you have any idea why this instability started showing up first in Firefox? As I mentioned, Firefox started crashing every time I closed a tab. The whole thing went down. It would offer to restart, and when I approved that, I could close the tab that had crashed it. But when I closed a different, other tab, it would crash again. Could a corrupted .NET framework cause that problem?

And, finally, how can I get Windows to recognize a new hard drive?

I really appreciate your help.

 

[NoelDP]

Taking your questions in order
1) The 'Get new featues....' offer is a lead-in to offering an Anytime Upgrade to a higher edition - not a service pack.

2)I dislike FireFox - it requires way too many add-ins to be a useful browser, and they all have their foibles. I usually use IE or Chrome. As far as I know it doesn't use .NET at all.

3) New HD - open Disk Management (diskmgmt.msc) and find the disk there - right-click on it and select Initialize, then partition and format it, and assign a drive letter.

 

[mjf]

Each to their own. I like FireFox and run it on all my PCs. I found IE more flaky and gave it up some time ago - maybe it has improved.

 

[sinned]

Trying to initialize disk 1

Hi again, Noel:

I don't mean to whine, but right-clicking in my version of "diskmgmt.msc" doesn't bring up any option I recognize as Initialize, and no options I recognize as "partition" or "format". I would like to use the disk in a single partition, and formatted as an NTFS disk, which is what I see disk 0 as [in this view]:

View attachment 256688

To get this view, I first right-click on disk 0, then right-click on properties, then, on the volume tab, select disk 0 and click on the properties "properties" button again, where I should be able to name the disk. But when I try that path for disk 1, I get the view in the following screen:

View attachment 256699

I get the same result on D:, which is CD-ROM 0. When I look at the driver tab on disk 1, I see this:


View attachment 256702

Perhaps I should re-start the last few postings as a separate thread, but I don't know how to do that. Why don't I get an "initialize" option when I use Disk Management? I have been trying to read through the help screens for Adding Hard Disk Drives [which I printed off at 22 pages], but most of those seem to refer to the topic under Windows Server 2008 or Windows Vista. What am I doing wrong that I can't find an "Initialize" option so that I can partition and format the drive, and assign it a drive letter? And is there any way to assign it drive letter D:, and re-assign the DVD-ROM as E:?

 

[NoelDP]

It looks as if the disk has already been initialized - but not partitioned or formatted.

You have to partition it before you can format it -

1. In Disk Management, right-click the unallocated space on the dynamic disk on which you want to create the simple volume, and then click New Simple Volume.
2. In the New Volume Wizard, click Next, click Simple, and then follow the instructions on your screen.

 

[sinned]

The right right-click

Okay, Noel, I think I may have found it. Whilst looking at Disk Manager and showing my younger brother how I couldn't get an initialize screen, I noticed the legend at the bottom that says "Unallocated" is in black and "Primary partition" is in blue, as in this screen shot:

View attachment 256712

When I right-clicked on the black bar on drive 1, the bar indicating that the entire disk was unallocated, the system responded with a "New Simple Volume Wizard" that looks like this:

View attachment 256713

Since what I wanted was a volume on a single disk, I clicked "Next", and saw this:

View attachment 256714

So I opted for the maximum disk space and clicked "Next", and saw this next screen:

View attachment 256715

After assigning the disk letter "E" (I would have preferred it be D, but the system assigned that letter to the DVD-ROM drive), I clicked "Next", and saw this:

View attachment 256717

After which, when I clicked Finish, the Wizard finished and activated the disk. It looks like you were right, Noel, that the disk was already initialized, and only needed to be formatted -- I did exactly what you were probably at the time writing that I should do. Thanks for your help.

 

[NoelDP]

You're welcome - good luck with it!