CO-Release Build 21364 to Dev Channel + KB5003397 + KB5003402 to .1011

Coming down now.

Just servicing. It does NOT fix the .NET error.

Second machine, updated directly from current build 19042.962 to 21364.1, same problem with kb5001030.

Me too . . 

Why start a new thread?? I deleted your new thread,

because you already mentioned it here and it is now

added to the Known Issues in the Blog.

Second machine, updated directly from current build 19042.962 to 21364.1, same problem with kb5001030.

Me too . .

With mine it installed successfully April 15th and presented/has presented no error, problems or issues.

Cheers,
Drew![Image](https://learn-attachment.microsoft.com/api/attachments/2cb4303a-95cc-4622-aaba-7d885315471a?platform=QnA

Drew this issue is new to build 21364.

It has nothing to do with the last build.

It is now in the Known Issues.

I have the update error for .NET on 1 PC and

it never saw the update on the other PC.

For the problem of USB printers that is written in the Blog as solved and instead is not solved since there are several users who have problems with USB printers, what do we do? is there a solution in the next builds or do we need to switch to another operating system?

https://aka.ms/AAbw91b

https://aka.ms/AAc177k

https://aka.ms/AAc1f0g

https://aka.ms/AAc1f0i

These are preview builds in the Dev channel. There is a high likelihood you will encounter issues from time to time, and yes, some things take longer to fix than others. There was an issue that was fixed in this build that was believed to be the cause. It appears there may have been a second issue that is being investigated. If hitting issues with printers on Dev Channel builds is causing an impact on your such that you feel switching to a different OS is the solution, may I suggest using Release Preview, or retail builds. 

Appreciate your patience while we continue to investigate.

Also, I appreciate the feedback links for reference.

-Eddie

Yes, but considering that the problem was not solved in the end because those who in the last version reported the problem still detect this anomaly would it not be appropriate to update and correct the one written in the Blog? more than anything else because if someone sees that the problem is described as solved and then discovers that it is not it is not a good thing

With mine it installed successfully April 15th and presented/has presented no error, problems or issues.

Cheers,
Drew![Image](https://learn-attachment.microsoft.com/api/attachments/2cb4303a-95cc-4622-aaba-7d885315471a?platform=QnA

Drew this issue is new to build 21364.

It has nothing to do with the last build.

It is now in the Known Issues.

I have the update error for .NET on 1 PC and

it never saw the update on the other PC.

For the problem of USB printers that is written in the Blog as solved and instead is not solved since there are several users who have problems with USB printers, what do we do? is there a solution in the next builds or do we need to switch to another operating system?

https://aka.ms/AAbw91b

https://aka.ms/AAc177k

https://aka.ms/AAc1f0g

https://aka.ms/AAc1f0i

These are preview builds in the Dev channel. There is a high likelihood you will encounter issues from time to time, and yes, some things take longer to fix than others. There was an issue that was fixed in this build that was believed to be the cause. It appears there may have been a second issue that is being investigated. If hitting issues with printers on Dev Channel builds is causing an impact on your such that you feel switching to a different OS is the solution, may I suggest using Release Preview, or retail builds. 

Appreciate your patience while we continue to investigate.

Also, I appreciate the feedback links for reference.

-Eddie