Recent content by larysid

Hello! Does anybody knows what's going on with these sdk updates? I have already installed (to my Desktop PC and dell laptop) the June's latest windows app runtime main, singleton and DDLMs (x86 and x64) for both versions (2.2.0 and 1.8.9). I successfully received yesterday the latest windows...

Everything went also fine here 🙂 It seems that SCEP event viewer id 87 is gone after installing this update!

I don't face these errors to both of my machines 😕 Sorry...

Yes you are right! Nothing to worry about as my friend above said! Just ignore it... classic ms bugs...

Fixed!!! Microsoft has also triggered a new error to the event viewer after this update: SCEP certificate enrollment....event id 87... Classic Microsoft bugs🤣

It was too good to be true...i have to run dism restore for second time to my pc, because after pc restart, the dism scan health is shown repairable again. The laptop, on the other hand, showed the dism scan health repairable but the dism restore health showed the classic error: " the repair...

If you are not sure, then rerun dism scan and check health again and sfc of course..

Yes I read that this will be gradually released to users machines!! It's nothing to worry about! I was just wondering!!!

Just out of curiosity 😂 why I have not received yet the pick a date to choose to the pause updates tab? I still have the "pause 1 week etc". It is funny because it's been a month since I have formatted my custom PC.. Maybe I have to wait .. However my dell laptop shows this pick a date option...

It's fine!

Everything went fine here! Is it necessary to run again (for a second time) sfc /scannow after the dism start component cleanup??? It takes too much time to finish... Prior to these: Dism scan and check health are clean, the same as sfc /scannow..

Guys you are all right above! We don't know why these dcom {0000....0000} errors appear (sometimes at shutdown) and which app is the culprit...I cannot also explain which is at fault regarding the yellow warning dcom error CLSID{00000000-0000-0000-0000-0000000000}...As I have already seen...

No problem here.. everything is shown fine when I choose to delete it (as you showed to us above with just one file)...in case you have not messed up with registry or system32 or done sth not recommended by microsoft (running scripts for example), then it will be soon fixed by itself after the...

Just wait...I am pretty sure it will be fixed to everyone soon... However, it's not a big deal!!! 😉 Personally I don't face this bug...

Mine seems to be good, for the time being..maybe it's a matter of time to be gradually fixed to everyone...