Windows 10: Should these event entries worry me? Solved

Page 1 of 2 12 LastLast
  1.    12 Jul 2016 #1

    Should these event entries worry me?


    I am still seeing unexpected restarts, though not as many as prior to upgrading from 7 to 10. However the event logs around today's restart were are a bumper crop, of which some I have not seen before. I hope someone will look at what I post below and advise me, please, if there is anything there to be worried about. For instance why the entry about Windows.old, removed as no longer required, is puzzling. Could my system be on the blink?

    Code:
    The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_
    Generic-&Prod_Compact_Flash&Rev_1.01#058F63626420&1#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
    and other similar warnings
    Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Windows\Media Center\PvrRecoveryTask definition. 
    Additional Data: Error Value: %SystemRoot%\ehome\mcupdate.exe.
    Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Windows\Media Center\PBDADiscoveryW1 definition
    . Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe.
    and 16 other similar warnings
    The server service was unable to recreate the share Windows.old because the directory C:\Windows.old no longer exists.
      Please run "net share Windows.old /delete"
     to delete the share, or recreate the directory C:\Windows.old.
    Session "Pku2uLog" failed to start with the following error: 0xC0000035
    and 4 other similar warnings
    Name resolution for the name wpad timed out after none of the configured DNS servers responded.
    Installing printer driver Microsoft XPS Document Writer failed, error code 0x0, HRESULT 0x80070705. 
    See the event user data for context information.
    The print spooler failed to regenerate the printer driver information for driver Microsoft XPS Document Writer for environment Windows x64.
     Win32 system error code 1797 (0x705). This can occur after an operating system upgrade or because of data loss on the hard drive
    The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available.
     The first four bytes (DWORD) of the Data section contains the error code.
      My ComputerSystem Spec


  2. Posts : 3,854
    Mac OS Sierra
       12 Jul 2016 #2

    Looks like it got a hiccup during Housekeeping. Open a Command Window and run sfc /scannow and follow the info at DISM - Repair Windows 10 Image - Windows 10 Forums

    Always read the stickys on the forum and check the tutorials first for suggested repair options. If you run into further issues, post exactly what the problem is and any error messages.
      My ComputerSystem Spec

  3.    13 Jul 2016 #3

    Sfc /scannow gave clear report, but Chrome refuses to paste CBSLog or anything else anywhere. Do I need proceed further with current problem then, having the clear report?
      My ComputerSystem Spec

  4.    13 Jul 2016 #4

    It's OT but the paste problem does not arise if I use Edge or paste (but not post) the file contents in to another similar site to this, using Chrome. Here eventually the not responding notice comes up with "wait" or "kill". Some half dozen "waits" and still zilch.
      My ComputerSystem Spec


  5. Posts : 3,854
    Mac OS Sierra
       13 Jul 2016 #5

    Use Firefox or Chrome. Edge still has some toddler issues with still trying to walk. The logs have to be uploaded as a zip file, so that those who use Windows can read them. If the errors are going away when you ran the Dism and SFC tools, it could be just housekeeping from the change over.

    Most are doing the Upgrade, then doing a Clean Install to get past the errors and problems that are happening when 10 does not properly upgrade.
      My ComputerSystem Spec

  6.    14 Jul 2016 #6

    I'll leave it there then. and see what transpires. IIRC I did do a clean install after some other problems, with downloaded system disk.
      My ComputerSystem Spec

  7.    14 Jul 2016 #7

    Hi,

    The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_
    Generic-&Prod_Compact_Flash&Rev_1.01#058F63626420&1#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
    Open regedit and in the find box paste in the key put in bold and let it search for it.
    Right click the key on the left hand side and select delete.

    The error stems for a boot or restart with that device still pugged in.
    Another work around is to disable portable services in the services management console.

    The server service was unable to recreate the share Windows.old because the directory C:\Windows.old no longer exists.
    Please run "net share Windows.old /delete"
    to delete the share, or recreate the directory C:\Windows.old.
    That's all it takes.

    The other errors are either unfamiliar to me or I can't offer a solution for them.

    Cheers,
      My ComputersSystem Spec


  8. Posts : 8
    Windows 7 Pro 64-Bit
       30 Aug 2016 #8

    I'm getting this error and it's for the Samsung SSD 850 Pro I recently installed Windows Ten Pro on. A few point/questions.
    1. I did not know Windows considers this a portable drive. Why?
    2. The driver is from Microsoft, the year 2006! A search shows no newer driver.
    3. I would be hesitant to delete the registry key, even after backing it up because it's the main drive with Windows installed.
    4. My install is clean and not migrated from Windows 7 Pro, so there is no windows.old file. Did that once and couldn't stand the idea of having all the bloat and possible issues.
    Any suggestions?
      My ComputerSystem Spec

  9.    30 Aug 2016 #9

    Hi,

    That does not sound right assuming the drive is attached to a SATA port.
    Most MS drivers for W10 stem from 2006 though, so you shouldn't worry about that.

    If this is the only drive in your system then I suggest you'd take a full back up first then delete the key in question and see if the error goes away.
    In case it's not the only drive in your system then it may be that it boots from another drive and then considers your Samsung as a removable storage unit.

    Cheers,
      My ComputersSystem Spec


  10. Posts : 8
    Windows 7 Pro 64-Bit
       30 Aug 2016 #10

    Thanks for responding.
    I do have two other HDD's, but if I removed the SSD there is nothing on them to boot from. I don't mind a little experimentation, I have been making regular system images since installing Windows Ten Pro.
    I'm curious how this would fix the error, I believe Windows would just re-install the same driver again, and wouldn't the error come back?
    A more important question is what are the effects of the error?

    It did.
    Delete, reboot and it came right back.
    Last edited by Barefoot; 30 Aug 2016 at 22:45.
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
On the one hand it is great that PC gaming is showing a resurgence, and gamers can look forward to Tomb Raider and Quantum Break are coming to the Windows 10 Store. However, players are increasingly concerned about Microsoft’s track record when...
Hello everyone, I keep seeing this error appear several times a day, even during idle, in my Event Viewer. I did a clean install of build 10586 less than a month ago. I'm not having any overt issues yet, but the error is disturbing. ...
EDIT: ARGH, sorry, meant to post this in General Discussion forum, I have no idea if it is a network issue. Hello everyone, I keep seeing this error appear several times a day, even during idle, in my Event Viewer. I did a clean install of...
Clearing event viewer entries in General Support
How can I construct a .bat file to clear entries in the event viewer. Thanks
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:09.
Find Us