KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2  

Globespy said:

Perhaps try the only thing that worked for me (posted on the previous page). I had gone through every other option being suggested here:
KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2

Dism get capabilities ... "Capability Identity : Analog.Holographic.Desktop~~~~0.0.1.0State : Not Present"

Subsequent trial to remove it (against better knowing) logically yields
Error: 87A Windows capability name was not recognized.

Help! Can't get past 21H1 19043.899. Errors...retry with every attempt.

James Callan said:

Help! Can't get past 21H1 19043.899. Errors...retry with every attempt.

This seems to be a common theme, a lot of users had trouble getting from .899 to a newer update (me included). In the end I used the UUP Dump to get a 19043.906 ISO. I was able to get to .928 without problems. I think the .899 update broke something which stopped future updates working.

f14tomcat said:

I, also, had a devil of a time with this one on the Beta. I found that if I went back to 19043.844, the February level, restored it, all was smooth as glass.

May not be an option for all, but if you're stuck, and you have the 19043.844 on a backup you can restore, give it a try.

Yes there was definitely something wrong with the .899 Beta update

Thanks all, I'll pursue the options.

James Callan said:

Thanks all, I'll pursue the options.

The best/safest/most likely to work option is the in-place upgrade using the UUP Dump 19043.906 ISO. The .899 update can't be uninstalled (tried that first).

Appreciate some input here.
I am on build 19042.928, and can see this KB was installed successfully.

I am afraid to click install as I had awful trouble a few days ago with CU's causing errors (turned out to be WMR software in my case - found that tip on reddit from another user who was having the same issues with a string of CU's).
Should I just use the block tool to hide this since it's already installed?
Thanks for any feedback.