T Trenton New member Joined Jun 23, 2015 Posts 1 Jun 23, 2015 #1 I am experiencing a variety of Windows 8.1 problems. Internet explorer wont work - You're not connected to a network. Ping to www.google.com works I have reset tcp ip stack and winsock stack - Had problems doing this, but resolved these by changing register entry permissions. Network & Sharing Center stays blank for 10+mins then come up but shows a server error instead of network settings It also takes a long time for the Control Panel to come up - 10+mins blank before it will come up, the appears to work ok. System restore won't complete. In have run MalwareBytes, ADWCleaner, RogueKiller and TDSSKiller Event Log has many error like The server {A47979D1-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout. The Network List Service service terminated with the following error:The specified procedure could not be found. The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout. The Windows Audio Service terminated with the following error: The endpoint is a duplicate. I have tried sfc , it says it found faults but can't fix. I have run sfcfix and have attached the log. It cant fix it. Hope someone can help. Trenton View attachment SFCFix.txt
I am experiencing a variety of Windows 8.1 problems. Internet explorer wont work - You're not connected to a network. Ping to www.google.com works I have reset tcp ip stack and winsock stack - Had problems doing this, but resolved these by changing register entry permissions. Network & Sharing Center stays blank for 10+mins then come up but shows a server error instead of network settings It also takes a long time for the Control Panel to come up - 10+mins blank before it will come up, the appears to work ok. System restore won't complete. In have run MalwareBytes, ADWCleaner, RogueKiller and TDSSKiller Event Log has many error like The server {A47979D1-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout. The Network List Service service terminated with the following error:The specified procedure could not be found. The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout. The Windows Audio Service terminated with the following error: The endpoint is a duplicate. I have tried sfc , it says it found faults but can't fix. I have run sfcfix and have attached the log. It cant fix it. Hope someone can help. Trenton View attachment SFCFix.txt
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,134 Location United States Jun 27, 2015 #2 Hi and welcome to Sysnative. Sorry for the delay. The telemetry errors in your log can safely be ignored. It's a known issue that Microsoft is working on and doesn't impact the function of your machine. We can check one other thing and if nothing shows in the logs then the next step would be to post an inquiry in our Windows 8 forum. Let's check first though. Please do the following. Step#1 - DISM /RestoreHealth Scan Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Right-click on the Start button and select Command Prompt (Admin) When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead. copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread. Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Hi and welcome to Sysnative. Sorry for the delay. The telemetry errors in your log can safely be ignored. It's a known issue that Microsoft is working on and doesn't impact the function of your machine. We can check one other thing and if nothing shows in the logs then the next step would be to post an inquiry in our Windows 8 forum. Let's check first though. Please do the following. Step#1 - DISM /RestoreHealth Scan Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Right-click on the Start button and select Command Prompt (Admin) When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead. copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread. Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
R radagast Member Joined Jul 9, 2015 Posts 18 Jul 9, 2015 #3 This is very interesting. I'm having the exact same issue here with a system. 'tis also a Windows 8.1 machine and the `cbs.log` seems to have tested out clean, unless I missed something (I trusted a tool to analyze it, so I will need to go back and check). I'll run it here again and grab it from that system and post it for review. Unfortunately it seems to take >30 minutes to execute; hanging at the blinking cursor just under the "Image Version: 6.3.9600.17031" output for an exceptional length of time (`sfc` and `dism`). I'm very curious to see others having this somewhat recently and I am suspecting either some recent MS update or perhaps an undetected infection as I have been exceptionally thorough. Here is a duplication of this issue.
This is very interesting. I'm having the exact same issue here with a system. 'tis also a Windows 8.1 machine and the `cbs.log` seems to have tested out clean, unless I missed something (I trusted a tool to analyze it, so I will need to go back and check). I'll run it here again and grab it from that system and post it for review. Unfortunately it seems to take >30 minutes to execute; hanging at the blinking cursor just under the "Image Version: 6.3.9600.17031" output for an exceptional length of time (`sfc` and `dism`). I'm very curious to see others having this somewhat recently and I am suspecting either some recent MS update or perhaps an undetected infection as I have been exceptionally thorough. Here is a duplication of this issue.
R radagast Member Joined Jul 9, 2015 Posts 18 Jul 9, 2015 #4 So interestingly `dism` failed this round! Curious as to what I may have done to provoke this new result, but here is the log.
So interestingly `dism` failed this round! Curious as to what I may have done to provoke this new result, but here is the log.
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,134 Location United States Jul 9, 2015 #5 radagast - If you need assistance, please start your own thread and someone will get with you. Thank you.
radagast - If you need assistance, please start your own thread and someone will get with you. Thank you.
R radagast Member Joined Jul 9, 2015 Posts 18 Jul 9, 2015 #6 I'd prefer not to since this is precisely the same issue and issues should be bundled together. I can say with certainty that this is PRECISELY the same issue as the original poster. Why would you want another thread started?
I'd prefer not to since this is precisely the same issue and issues should be bundled together. I can say with certainty that this is PRECISELY the same issue as the original poster. Why would you want another thread started?
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,134 Location United States Jul 9, 2015 #7 Why would you want another thread started? Click to expand... Because if the original poster comes back it will be very confusing when replying back and forth as to who the information was intended for.
Why would you want another thread started? Click to expand... Because if the original poster comes back it will be very confusing when replying back and forth as to who the information was intended for.
R radagast Member Joined Jul 9, 2015 Posts 18 Jul 10, 2015 #8 Thanks for clarifying your desire for the new thread. I've created it as per your request here.
R radagast Member Joined Jul 9, 2015 Posts 18 Jul 11, 2015 #9 So @BrianDrab having started a new thread and outlined that which you previously asked, I am still not receiving a reply there... Did I do something wrong?
So @BrianDrab having started a new thread and outlined that which you previously asked, I am still not receiving a reply there... Did I do something wrong?
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,134 Location United States Jul 11, 2015 #10 Not at all. There are many people ahead of you at the moment. We normally have a 3 day response time but sometimes it can be a little longer based on volume.
Not at all. There are many people ahead of you at the moment. We normally have a 3 day response time but sometimes it can be a little longer based on volume.