Just curious, single event id 7011

Hi all!

Yesterday I 'shut down' Windows to this 'maintenance' screen where you can - among other things - choose to boot from a usb-stick or dvd. Needed to do so because I had to check created boot media for Macrium. Anyway, that all worked great etc. Later, when looking at the logs (which I always do after a start of Windows for some paranoid reason...) I found one curious EventID: 7011 considering a Time-out considering the service Appinfo. This happened before or during switching to the 'maintenance/recovery-whatever' blue screen with icond (how is that called in English anyway?). I guess it's nothing, but I am just curious what Appinfo is. And if I should worry or not :-D It never happened again, so yeah... I know I shouldn't worry too much about shutdown log entries anyway. But you know, Windows 10... )))




Greetings!

unfortunately, i cannot understand what appears to be German language but it appears to be related to the DCOM service and from what i can see, its not an error i would be overly concerned about unless you are actively using and developing with DCOM & MSDTC.
What is MSDTC and why do I need to care about it? Consistency Checkpoint
What is DCOM (Distributed Component Object Model)? - Definition from WhatIs.com

It's Dutch! DCOMM's I am not worried about at all, they are unavoidable since XP I think. This was related to a Service Host error with a timeout of something. I am not overly concerned, but after upgrading to the Creators Edition I am just looking - for now - a bit more regular in/at the logs. Most errors and warnings are pretty standard and ignorable. But sometimes I discover something new.

that said: since the upgrade to Creators, its's a lot more quiet in the logs. That's good, most upgrades lead to a host of new errors and noticable problems. So far, this is not the case yet here. I also have the feeling that there are less major problems with this upgrade in comparison with former ones. Although the number of people who get stuck during the upgrade seems to be still too high, unfortunately. Anyway, let's hope things stay like this, knock knock knock...


greetings from Holland!

Win10usr said:

Hi all!

Yesterday I 'shut down' Windows to this 'maintenance' screen where you can - among other things - choose to boot from a usb-stick or dvd. Needed to do so because I had to check created boot media for Macrium. Anyway, that all worked great etc. Later, when looking at the logs (which I always do after a start of Windows for some paranoid reason...) I found one curious EventID: 7011 considering a Time-out considering the service Appinfo. This happened before or during switching to the 'maintenance/recovery-whatever' blue screen with icond (how is that called in English anyway?). I guess it's nothing, but I am just curious what Appinfo is. And if I should worry or not :-D It never happened again, so yeah... I know I shouldn't worry too much about shutdown log entries anyway. But you know, Windows 10... )))




Greetings!

one of the interesting things i discovered after updating to the creators update 1703 is that most every service that starts (services.msc) is now contained in its own service "host" (svchost.exe) where the previous build would have several services operating under a single service host.
this can be observed through process explorer (3rd party app).
so if you had 40 services starting, each one has its own host instead of combining half or more under a single host.
i suspect this is a redundant safety measure for the creator builds (otherwise known as a beta) in the event a single service should "crash" since each service has its own host independently, it doesnt affect additional services running.
i actually like this idea better instead of 20 services under a single host.

True. I red that this trick only works with computers that have at least 4GB ram (which nowadays more or less every system of course). It also leads to much faster starts. Yes, the Windows desktop was always quickly available, but it took about five minutes before HD activity calmed down. The great hogs were the processes that started 10 to 20 processes under its wings. If you did something critical during the time those processes were not fully started, weird things could happen. Since Creators Edition that problem doesn't exist anymore. Makes one wonder why MS didn't do it like that from the beginning on.

Greetz!

EliteData said:

one of the interesting things i discovered after updating to the creators update 1703 is that most every service that starts (services.msc) is now contained in its own service "host" (svchost.exe) where the previous build would have several services operating under a single service host.
this can be observed through process explorer (3rd party app).
so if you had 40 services starting, each one has its own host instead of combining half or more under a single host.
i suspect this is a redundant safety measure for the creator builds (otherwise known as a beta) in the event a single service should "crash" since each service has its own host independently, it doesnt affect additional services running.
i actually like this idea better instead of 20 services under a single host.