Windows update1809 and 1903 fails from June 18 on

[Sankar_M]

I have HP Pavilion dv6 Notebook PC running Windows 10 Home 64-bit Version: 17134.1006. The computer is still running well but Windows Update scheme wants to update to 1903 and after 3 hours of installing and restarting on its own it invariably fails.

I checked Windows answers blog but all that fails also. Now, I check HP site  and it lists a whole lot of HP pavilion that are cable of updating but not mine.

Does that mean I should give up? Windows will stop supporting 1803 very soon. It probably means I have to switch to a new computer. But believe me I will buy another Mac, not Windows PC.

Regards.

[WAWood]

@Sankar_M 

I have \an HP DV6 laptop and it is running Win10 v1903 without any issues.

You're probably trying to do the Feature Upgrades using Windows Update -- which is the least reliable and most error-prone way of doing it.

A much more reliable method is doing an in-place Upgrade using Windows 10 media -- which you can download and create using this link:  Windows 10 download

Then when you have the media, insert it into your PC (do NOT boot from it), find the folder containing the files, right-click setup.exe file and select Run as Administrator.  It should take a couple of hours or so to do the Upgrade.

[Sankar_M]

Hi,

Thanks but I have tried creating media tool etc. Because the update 1903 fails and a lot of Microsoft community members suggest that.

But after all that and trying some other suggestions, they still don't work. 

IThanks anyway.

[Sankar_M]

Here is what I did.

1. My updates failed from 6/7/2018. I had 1803 version. Windows tried their update but it failed all the time.

2. Most of the microsoft community people suggested to use iso file for clean install. I tried that and it failed also.

3. I looked at the Panther log file and it had some errors. Someone in Microsoft community also suggested it could be IIS error. I went back to the log and saw it does complain about iissetup.exe.

4. So, I disabled IIS. Got an error but then booted in safe mode and renamed inetsrv to inetsrv.old. Then, disabled IIS.

5. Then, went back and used Windows Update again and it chugged along for 3 hours and it worked. Now my winver is 1903.

6. I am not sure why Microsoft does not issue a patch for this. It seems to be a common issue.

7. Thanks to all other people who suggests in this community.