Replies

PKCano, thanks for the clarification. Seems logical, but with MS, one never knows.

I realize the update issue of KB5000802/KB5001649 was asked earlier, but I regret that I did not understand the answer.

I have not yet installed any March updates.  After downloading KB5001649,

1–Do I hide …802 before installing …1649? Then after installing …1649, should ..802 be “unhidden” to dispose of it as MS sees fit? OR

2–Not hide …802 and leave it in the processing queue along with …1649 and let MS sort it out during the update installation process?

Thank you for helping me understand this as I am sure this updating process issue will surface again.

 

As the OP, I recently updated our aging iPhone 7’s to v14.4 from the latest version of 13.

Tried using iTunes that is installed on a Win7 laptop that I always used. I updated to latest version of iTunes for Win7 (think it is v12.7). Both phones failed after the extraction phase with the message “The iPhone “name” could not be updated. An unknown error occurred (4000).” Not very helpful to say the least. I tried each phone twice with the same result. So much for iTunes at least on Win7. As horrible as it is, I have never had an iTunes error. Maybe I would have had better success either with newer phones or iTunes on Win10, or both.

I then did an OA update; seemed to take forever. On both phones, there was an error message that it could not process the update. I hit the Retry option and the update installed  on both.

Hopefully there will not be another urgent iOS update soon. So long iTunes.

Thanks to all who responded.

Per your suggestion, I will set “Preview Builds…” to “SemiAnnual Channel” and leave it at “0” deferral days. Maybe that will eliminate some of  the Previews.

I suppose this setting (Preview Builds..) will not interfere with getting the 20H2 version once I set the TRV to “20H2” that we will probably have to get by this fall.

Thanks so much for your helping me understand the W10 updating process.

 

PKCano,

Not to belabor the GP settings under Windows Update for Business, I have set the TRV to be “2004”. I have not set/enabled the Preview Builds and Feature Updates…” as I missed that along the way.

I was under the impression that “Preview Builds….” did not need to be set/enabled if the TRV was set. No problem setting it to “SemiAnnual Channel” if it needs to be. If this is set, I suppose there would be no problem in getting the 20H2 version if TRV is set to “20H2”.

All of this will probably change again in the 2021 versions.

Thanks.

[hms]

Same happened in my update to 2004. The 2004 Update file showed up first in wushwhide as an update that could be hidden. It was not shown in the normal Windows update window. I turned off the pc for the day. I did not check it in wushowhide. The next day the update file showed up in the normal Windows update window. From that window I did the install. Why did it first show up in wushowhide? I have no idea but it did.

• This reply was modified 4 years, 2 months ago by hms.

1 user thanked author for this post.

BobbyS

I updated yesterday from 1909 to 2004 (pro)  without disconnecting although I do not know if that is recommended.  I made sure that the queue was cleared except for the 2004 update file. All of my group policy settings carried over such as TRV, 3rd party driver setting, etc.

However, other settings/configurations were not such as system restore had to be reset/restarted; disabled fast startup again, and a couple of others. Since I already have a 2004 pc here, it was easier and I had made a note of the system changes I had made along the way.

The update went well; took about 1 1/2 hrs, – could have reduced time, but I let it sit awhile before restarting  that may not have been necessary.

After the update to 2004, a .net patch from October (KB4578968) and the adobe remover patch (KB4580325) were offered which I installed today.

The only problem that I see is the multitude of Event 642 ESENT warnings in Event Viewer that were not present in 1909. But they have been there on my other 2004 pc for months and have presented no problems. Apparently no easy fix for that issue.

Hope all goes well.

1 user thanked author for this post.

jburk07

This probably explains the shutdown error msgs that I rec’d during a turn off/turn on (not restart). I have not noticed lags in startup with Fast Start disabled although I have not timed it to the second.

Noticing your comment about turning off Fast Start, I had to turn Fast Start off for both my 1909 and 2004 pcs. They were randomly giving off error reports in reliability history that Windows was not shut down correctly. That was not true. After turning Fast Start off (not recommended by MS), I have not rec’d this error msg. in months. Also, I do not notice any lag in startup – although both have SSDs.

Based on your and Rick’s comments about using iTunes, suppose it is iTunes for our iPhones as weare still on v13.7 so going to 14.4 would be a big jump. I put off updating iOS because 1) one never knows the problems that will come up, 2) I really hate using iTunes, and 3) new iOS versions never give me anything substative other than security updates (the same as Windows) although I never use iPhones for banking, etc.

Thanks again for your comments.

I do not have set to automatically update. It downloads about 2 weeks or so after the update is released and reminds me to install the update .

From what I read, v14.4 is recommended for security purposes, so I suppose I should manually download it rather than waiting 2+ weeks.

Thanks for both of your replies. However, I am not familiar with .ipsw files, so I should skip that.
To update, do you request the Download & Install or wait for the device to download on its own that may take 2 weeks or so and then install.

The phones had v14.3 downloaded, but I did not install. Now that option is gone since v14.4 has arrived and may be 2 weeks or more before it automatically downloads v14.4.

Thanks

Per your suggestion, I have hiden these; presumably hidden updates  will not install with the new 2004.

I had not hiden these MS drivers as I thought the list would not expand as newer updates would replace the older ones. Suppose I was wrong; the list, especially for Realtek audio, keeps growing, but Dell says I need only 1 Realtek optional update that I never bothered to install for an inexpensive speaker.

Will do the 2004 update once Defcon changes from 2.

Thanks again for your help.

Before updating to 2004 by TRV, should I hide a raft of third party Intel and Realtek updates? I did hide KB4535680 and one other earlier KB.

I have set by Group Edit to Not Include Drivers with Win Updates. They are just sitting there as I have not hidden them. Should they be hidden before updating?

Will my Group Edit policy settings be carried over to 2004?

I have installed some Intel updates through Dell update so some of the windows version Intel updates may already be installed by that process.

I want to avoid having the 2004 automatically update all these Intel and Realtek updates.

Thanks.

I will wait a week or so to see if any major Jan. update problems and will avoid the Secure Boot patch.

Thanks  so much.