Aurora R7, update problem

Possibly, but that is a Microsoft problem.

Have you tried the Troubleshooter for Windows-Update?

What is the KB number?

ah. yes ive tryed the updater and it did not work.

KB4338819

This will take some research. My guess right now is that KB4338819 has been superseded, or there is a missing prerequisite update.

On the v1803 machine I just checked ... it it "up-to-date", but KB4338819 is not listed in Installed History (but a higher-numbered one is installed).

Here are some general tips and notes for Windows-Update:

- Switch your machine to the update-ring for Organization and Business. This provides time for patched superseded updates to be released, and then only those "fixed ones" ever install.

- Yes, I've seen something like this before. Sometimes you have to wait for the next full-milestone release to be installed to fix it. For example, if this was going-on on v1709, when v1803 finally installs, it usually fixes it.

- When a full-milestone update installs (like v1803) it resets all the logs (Update History and Windows Reliability Report)

Here are my (abridged) notes about general Windows-Update checks/fixes:

The first thing you need to do to see if your "component stores" it corrupted and to see if it repairable is to open command prompt as ADMIN,
after you have opened that you need to type this :
dism /online /cleanup-image /scanhealth

This will let you know if there is a problem with your windows.
If it says "No Component Store Corruption Found" ... you are done.
- So, go to Updates and see if you can be "up to date".

Then run this to see if its repairable.
dism /online /cleanup-image /checkhealth

This will tell you if it repairble or if there is a problem with your windows.

If it is not repairable you will have to either try to repair it with an "over-lay install" with DVD/USB-Installer or most likely do a clean install.

If it is repairable you will then run this command:

dism.exe /online /cleanup-image /restorehealth

If it fails, and stops early, try again.

==============================

You can also open an Elevated Command Prompt, for a full system scan and have SFC attempt repairs:
sfc /scannow

I think SFC checks currently used Windows files, while DISM is for the Windows Image ... used for installs, updates, and reconfigs.

What I get after trying the methods mentioned, is error 87..Cannot get past this error.

My brand new Aurora A7 had the same issue last year and I tried and tried to fix it (with a very limited skill set).  Luckily it was within the return period at Best Buy so I just took it back.  The exact same model has been working fabulously over the past year except for the fact that everyday it asks me to update my bios....  

The frustrating part of this whole thing was that it was the Alienware Update tool that caused the issue but Dell support insisted that it was a Windows problem (much like above). Anecdotally the problem hasn't occurred since I've avoided the update...

---

@Tesla1856 wrote:

Here are my (abridged) notes about general Windows-Update checks/fixes:

The first thing you need to do to see if your "component stores" it corrupted and to see if it repairable is to open command prompt as ADMIN,
after you have opened that you need to type this :
dism /online /cleanup-image /scanhealth

This will let you know if there is a problem with your windows.
If it says "No Component Store Corruption Found" ... you are done.
- So, go to Updates and see if you can be "up to date".

Then run this to see if its repairable.
dism /online /cleanup-image /checkhealth

This will tell you if it repairble or if there is a problem with your windows.

If it is not repairable you will have to either try to repair it with an "over-lay install" with DVD/USB-Installer or most likely do a clean install.

If it is repairable you will then run this command:

dism.exe /online /cleanup-image /restorehealth

If it fails, and stops early, try again.

==============================

You can also open an Elevated Command Prompt, for a full system scan and have SFC attempt repairs:
sfc /scannow

I think SFC checks currently used Windows files, while DISM is for the Windows Image ... used for installs, updates, and reconfigs.

---

If the above fails, then I'd start looking at software conflicts.  It took me over a month to discover that an anti-cheat system resource was installed by Steam, causing slow and fast ring insider updates to break.  Removing that corrected the issue immediately.