Latest Windows 10 Update

%3CLINGO-SUB%20id%3D%22lingo-sub-2202400%22%20slang%3D%22en-US%22%3ELatest%20Windows%2010%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2202400%22%20slang%3D%22en-US%22%3EAn%20update%20came%20thru%20Wednesday%20Night%203%2F10%2F2021.%20My%20edition%20on%20Windows%20is%20Windows%2010%20Home%20version%202004%20installed%2011%2F16%2F2020%20OS%20build%2019041.867.%20After%20the%20update%20file%20names%20on%20my%20desktop%20have%20weird%20characters%20taskbar%20has%20the%20same%20characters.%20Unable%20to%20uninstall%20the%20latest%20update.%20Does%20anyone%20have%20a%20solution%20to%20this%20problem%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2208621%22%20slang%3D%22en-US%22%3ERe%3A%20Latest%20Windows%2010%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2208621%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3Ethat's%20very%20strange.%3CBR%20%2F%3Eif%20you%20are%20using%20Windows%20security%20(Defender)%2C%20please%20make%20sure%20Windows%20and%20Defender%20are%20up%20to%20date%20and%20then%20perform%20a%20full%20scan%20of%20the%20system.%3CBR%20%2F%3E%3CBR%20%2F%3Ealso%20check%20in%20Windows%20settings%20%3D%26gt%3B%20Time%20%26amp%3B%20Language%20%3D%26gt%3B%20Region%20%3D%26gt%3B%20Regional%20format%20and%20make%20sure%20it%20is%20correctly%20set.%3C%2FLINGO-BODY%3E
New Contributor
An update came thru Wednesday Night 3/10/2021. My edition on Windows is Windows 10 Home version 2004 installed 11/16/2020 OS build 19041.867. After the update file names on my desktop have weird characters taskbar has the same characters. Unable to uninstall the latest update. Does anyone have a solution to this problem
4 Replies
Hi,
that's very strange.
if you are using Windows security (Defender), please make sure Windows and Defender are up to date and then perform a full scan of the system.

also check in Windows settings => Time & Language => Region => Regional format and make sure it is correctly set.
Thanks for the information. I also researched Google. They suggested to do another Windows update. Another update (Kb4601554) came thru and corrected my problem

@Dgrfred 


@Dgrfred wrote:
Thanks for the information. I also researched Google. They suggested to do another Windows update. Another update (Kb4601554) came thru and corrected my problem

That's good to know it solved your problem :)