This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Greetings all,
a couple of days ago my PC was prompted to install KB5015730 (Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64). This was a single update. After the 'install' phase a restart was required. However, the after the restart my screen was completely black, although my cursor was still visible and I was able to move it around. I left my PC for a reasonable amount of time to see if anything would resolve itself but all that happened was the disk activity stopped (or, at least, appeared to do so). Eventually, I shut down my PC and then restarted it. This time I was presented with the usual blue 'updates' screen, informing me that my updates were 100% complete. A while after this my PC returned to its normal 'pre-login' screen and I was able to login without problem.
I should also tell you that I had a similar problem when I installed KB5012157 ( (Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64)). This also was a single update.
However, I have installed updates for "Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64" on other occasions but in conjunction with other updates and I've had no problems.
Does anyone have any idea as to what's happening here?
Kind regards.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
To see what happened, I recommend you look into Event Viewer and observe logs and you might find some clue what might have cause the issue. More likely there have been some failure during the installation.
You should also try check your device's manufacturer website and download and install all updates for drivers.
In addition, open start and search for feedback and open the Feedback Hub app and report this issue.
Hi @Reza-Ameri ,
many thanks for your reply. I've checked my event log but I can find no indication of the problem that I experienced. It does show where I had to re-boot but it doesn't show anything about the update seeming to halt while installing. Also, as far as I know, all my drivers are up to date.
The only thing that stands out to me is that each time this problem occurred I was installing that particular update on its own, not in conjunction with other updates. As I mentioned before, when I installed that update in conjunction with other updates I had no problems.
Kind regards.
Windows Update also save log files on number of locations including
C:\Windows\Logs\WindowsUpdate
C:\ProgramData\USOShared\Logs
%systemroot%\Logs\CBS
To learn more, have a look at:
https://learn.microsoft.com/en-us/windows/deployment/update/windows-update-logs
Hi @Reza-Ameri ,
I'll have to look into this a bit more. So far all the files in the 'WindowsUpdate' folder are 'Windows Performance Analyzer Trace File' files. I've never used the Windows Performance Analyzer before and I'm not even sure if these are the right files to check. I'll get back to you when I done a bit more investigation.
Kind regards.
The Performance Analyzer is related to the performance of the system and has nothing to do with the Windows Update.
The log files are the one which I shared and the one explains on the website.
If you won't see them, probably log files didn't create.
Hi @Reza-Ameri ,
I just created the WindowsUpdate.log file with the PowerShell 'Get-WindowsUpdateLog' command and I've been looking at the output. First of all, there's so much of it. I think I found the time stamp when things 'stopped' but I can't see any indication of why it happened - there's just so much going on and it doesn't really explain what happening.
Kind regards.
This is public forum, and it is not recommended to share the entire log files due to privacy.
However, if there is any part of the log files which you might need help, you may share it here so we could guide you.
Remember, don't share the entire log file but instead share the part where you might need help to analyze (make sure remove all personal data before doing so).
Hi @Reza-Ameri ,
I've had to reply to you via 'Write an Answer' as the 'normal' reply is limited to 2000 characters and I think I need more. Anyway, there are two sections in the Windows Update Log file which may be relevant. They cover two periods of inactivity, one between 15:31 and 15:50 the other between 15:55 and 16:30.One of these periods is when I re-booted - I'm not sure which is which but then again I'm completely unfamiliar with the Windows Update Log file. The two sections are as follows:
Section 1:
2022/08/01 15:31:10.4225496 17120 14872 Misc datastore uninit
2022/08/01 15:31:10.4837891 17120 14872 Misc setting cache uninit
2022/08/01 15:31:10.4837906 17120 14872 Misc security checker uninit
2022/08/01 15:31:10.4837931 17120 14872 Misc Test Hook uninit
2022/08/01 15:31:10.4837938 17120 14872 Misc IdleTimer uninit
2022/08/01 15:31:10.4847709 17120 14872 Shared * END * Service exit Exit code = 0x240001
2022/08/01 15:50:57.5279990 22412 24176 Shared InitializeSus
2022/08/01 15:50:57.5288711 22412 24176 IdleTimer Non-AoAc machine. Aoac operations will be ignored.
2022/08/01 15:50:57.5293133 22412 24176 Agent WU client version 10.0.19041.1806
2022/08/01 15:50:57.5296412 22412 24176 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2022/08/01 15:50:57.5299758 22412 24176 Agent Base directory: C:\WINDOWS\SoftwareDistribution
2022/08/01 15:50:57.5315614 22412 24176 Agent Datastore directory: C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb
2022/08/01 15:50:57.5331766 22412 24176 DataStore JetEnableMultiInstance succeeded - applicable param count: 5, applied param count: 5
2022/08/01 15:50:57.5993524 22412 24176 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2022/08/01 15:50:57.5995660 22412 24176 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
2022/08/01 15:50:57.6023796 22412 24176 Shared Network state: Connected
2022/08/01 15:50:58.9067034 22412 24176 Misc The volatile RebootRequired key exists
Section 2:
2022/08/01 15:55:42.8649286 22412 24176 Misc datastore uninit
2022/08/01 15:55:43.6617500 22412 24176 Misc setting cache uninit
2022/08/01 15:55:43.6617518 22412 24176 Misc security checker uninit
2022/08/01 15:55:43.6617544 22412 24176 Misc Test Hook uninit
2022/08/01 15:55:43.6617551 22412 24176 Misc IdleTimer uninit
2022/08/01 15:55:43.6625949 22412 24176 Shared * END * Service exit Exit code = 0x240001
2022/08/01 16:30:03.2728007 9280 9504 Shared InitializeSus
2022/08/01 16:30:03.2757549 9280 9504 IdleTimer Non-AoAc machine. Aoac operations will be ignored.
2022/08/01 16:30:03.2781735 9280 9504 Agent WU client version 10.0.19041.1806
2022/08/01 16:30:03.2794682 9280 9504 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2022/08/01 16:30:03.2803309 9280 9504 Agent Base directory: C:\WINDOWS\SoftwareDistribution
2022/08/01 16:30:03.2848757 9280 9504 Agent Datastore directory: C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb
Does this make any sense to you?
Kind regards.
Thank you for the log file, it shows everything is normal and it doesn't show any error message.
Normally errors would show like fail or error follow by a code.
Exit is normal process and doesn't necessary mean error.
There is possibility that error didn't log or might be in different log file.
Hi @Reza-Ameri ,
many thanks for your reply. I'm confused about this. The log file shows two periods of inactivity and, from what I remember, one of them coincides with me re-booting my PC because, although I could move the cursor around, the screen was totally black and there seemed to be no other activity going on in side my PC (the disk activity light wasn't on). As you can see from the log, the periods of inactivity were considerable (20 minutes approx in one case and 35 minutes approx in the other). Surely this can't be right can it? Do you think that if I had left my PC alone, rather than rebooting it, that it would have sorted itself out by itself? What should I do if this happens again with the same (or a different) update?
Kind regards.
Hi @Reza-Ameri ,
I thought you should know about this; I've just installed KB5016592, which is an update for the same 'Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64' item. This time, after the reboot, it stalled on a black screen (with the 'dots' circling) and no disk activity. I stopped and started the PC and it came up with a blue screen saying 'Please Wait', again with the 'dots' circling. Then the dots 'froze' and I had to stop and start the PC again. This time it came up with the 'normal' blue screen counting the update percentage complete and then finally finished normally (i.e. I was able to log in). This only ever happens with this particular update when it is installed on its own. I don't have any problems with other updates. This can't be right. Do you have any ideas as to what's happening?
Kind regards.
Hi @Reza-Ameri and anyone else who's interested,
I installed KB5017858 (which is Cumulative Update Preview for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 21H2 for x64) on 28th September 2022 and it installed without the previous problems I've been getting with this update. I can only assume that MS have fixed the problem so I'm going try to mark this answer as the 'Answer', if I can, unless or until it happens again.
Kind regards.
