1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Errors after 1-9-18 Windows Update

Discussion in 'Windows 8' started by nigebirch, Jan 13, 2018.

Thread Status:
Not open for further replies.
Advertisement
  1. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    Windows 8.1 Professional with Media Center (x64) (build 9600)
    Boot Mode: UEFI with successful Secure Boot
    Hewlett-Packard HP ENVY TS 17 Notebook PC
    Haswell chip Intel, SATA HD

    No problems with my system or laptop until I installed latest Windows updates 1-9-18 which included "fixes" for Spectre, Meltdown, et.al.

    Noticed that I could no longer view Event Viewer. When clicking on Event Viewer to check status after updates, I got the message that "MMC could not create the snap-in" (no CLSID nor other info was given). Went to MMC in an attempt to create the snap-in, but the option to create a snap-in for Event Viewer was not there.

    I noticed no other abnormalities and ran a scan disc from the Admin command prompt (sfc /scannow). It said it "did not find any integrity violations."

    In an attempt to fix my Event Viewer problem, I did a RESTORE from the restore point I created before doing the 1/9/18 Windows updates in order to remove these Windows updates. Everything went smoothly, but it did nothing to resolve my Event Viewer problem. To be sure other things were okay, I ran another scan from the admin command prompt and also ran the DISM (ScanHealth, CheckHealth and RestoreHealth) checks. All operations completed successfully with nothing needing repair. After doing the restore point to remove the updates, I used the laptop throughout the day and eventually clicked on SHUT DOWN.

    This morning, I signed on and decided to check Windows updates to see if there were other updates pending. There were NO updates, and it said that I had never checked for updates! I checked "View update history," and it reported "You have not tried to install any updates." Finally, I clicked on "Installed Updates," and it showed a number of updates going back to 2/2014 when I purchased this HP laptop (none from 1/9/18, but a huge number of updates done on 1/8/18).

    I ran an Update Troubleshooter which reported a number of errors that it said it fixed. Afterward, Windows Update showed 7 new updates to download (which I did not download/install). Updates are:

    2018-01 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 on Windows 8.1 and Server 2012 R2 for x64 (KB4055266)
    Download size: 79.2 MB
    Update type: Important

    2018-01 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4056895)
    Download size: 307.3 MB
    Update type: Important

    2018-01 Security Update for Adobe Flash Player for Windows 8.1 for x64-based Systems (KB4056887)
    Download size: 20.7 MB
    Update type: Important

    **Microsoft .NET Framework 4.7.1 for Windows 8.1 and Windows Server 2012 R2 for x64 (KB4033369)
    Download size: 101.8 MB
    Update type: Recommended

    Update for Windows 8.1 for x64-based Systems (KB3150513)
    Download size: 1.3 MB
    Update type: Recommended

    Windows Malicious Software Removal Tool for Windows 8, 8.1, 10 and Windows Server 2012, 2012 R2, 2016 x64 Edition - January 2018 (KB890830)
    Download size: 6.2 MB
    Update type: Important

    **NOTE: All of these updates were checked to download with the exception of the 4th one marked ** above (Microsoft .NET Framework 4.7.1 for Windows 8.1 and Windows Server 2012 R2 for x64 (KB4033369).

    Why list this in the Windows updates if the square to install is not checked? This has never happened before. They are always ALL checked if they are listed, strange.

    Again, I did NOT perform these updates. Instead, I chose to do another sfc scan from the admin command prompt, and again it did not find any integrity violations. I ran the DISM checks, and here is what I got this time:

    I ran Dism /Online /Cleanup-Image /ScanHealth, it reported the component store was repairable.

    I ran Dism ..../CheckHealth and it reported that the store was repairable.

    I ran Dism .../RestoreHealth, however, it reported that "The restoration operation failed. Either the repair source was no found or the component store cannot be repaired. ERROR: 0x800f081f DISM failed. No operation was performed. For more information, review the log file."

    Not being computer-savvy, I have no idea what the entries in the DISM log mean nor what to do next. I certainly don't want to have to a system restore if there is anything that can be done to fix what's going on. I have on this PC programs that I paid a lot of money for and downloaded online, one application that I am unable to reinstall without buying a new software key. :(

    I fear that Microsoft pushed out some poorly-made roll-ups in an attempt to fix the Spectre/Meltdown problem with the Intel chipsets. I should have listened to the little voice in my head telling me NOT to install these updates. Guess I'm one of the sad guinea pigs. :(

    I pray someone here is able to help me. Thank you.

    nigebirch
     
  2. dmccoy

    dmccoy

    Joined:
    Oct 7, 2017
    Messages:
    4,489
    First Name:
    Darrin
    We can run through some troubleshooting shooting if you like but, I would recommend creating an image backup and then performing an in-place repair of Windows 8. This will not remove any of your files, programs, settings ect. If you want me to check your logs then perform the steps below for the event viewer tool

    http://www.intowindows.com/how-to-repair-windows-8-1-installation/

    Please download and Run the Event Viewer Tool
    http://images.malwar...om/vino/VEW.exe

    1. Run program as Administrator
    2.. Under Select log to query
    3. select System
    4. Under Select type to list
    Select:
    * Error
    * Warning
    Choose the Number of events as follows:
    Click on umber of events
    Type 20 in the box (1 to 20)
    Click the Run button (Notepad will open the log)
    upload files to next reply
    Rename to SystemLog or it will be overwritten

    Run these steps again Except at step 3.
    Select Application
    Rename log file to ApplicationLog
    Upload the files or Paste to next reply
     
  3. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    Thank you for your answer.
    The link you gave the the Event Viewer tool didn't work. :( Do you have another?

    Question: Is an AOMEI Backerupper backup sufficient to backup my entire system (including applications)?

    Thank you,

    nigebirch
     
  4. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    I found the tool you linked on Google and downloaded it and ran it per your instructions. All I got was the following with no logs:

    "Cannot find the C:\VEW.txt file. Do you want to create a new file?"

    When I clicked on 'yes,' nothing happened. When I ran it again and clicked 'no,' same thing, nothing.
     
  5. dmccoy

    dmccoy

    Joined:
    Oct 7, 2017
    Messages:
    4,489
    First Name:
    Darrin
    It has to be ran as Administrator. Please right click on the program and select run as Administrator from the menu.
     
  6. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    Sorry. Here is log ... thank you.

    Vino's Event Viewer v01c run on Windows 7 in English
    Report run at 14/01/2018 5:59:14 PM

    Note: All dates below are in the format dd/mm/yyyy

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Critical Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 12/01/2018 8:08:18 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 16/12/2017 6:00:35 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 15/09/2017 6:56:58 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 25/07/2017 2:34:17 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 07/07/2017 11:57:37 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 07/07/2017 11:36:42 PM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 07/07/2017 12:10:00 AM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 23/06/2017 2:31:53 PM
    Type: Critical Category: 64
    Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Apple iPod (location Port_#0004.Hub_#0002) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 23/06/2017 2:31:53 PM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 07/05/2017 2:25:42 PM
    Type: Critical Category: 64
    Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Apple iPod (location Port_#0004.Hub_#0002) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 07/05/2017 2:25:42 PM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 02/05/2017 3:38:22 PM
    Type: Critical Category: 64
    Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Apple iPod (location Port_#0002.Hub_#0002) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 02/05/2017 3:38:22 PM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 19/12/2016 3:12:41 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 17/12/2016 4:58:12 AM
    Type: Critical Category: 64
    Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Validity Sensors (WBF) (PID=0050) (location Port_#0014.Hub_#0002) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 17/12/2016 4:58:12 AM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 17/12/2016 4:55:56 AM
    Type: Critical Category: 64
    Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Validity Sensors (WBF) (PID=0050) (location Port_#0014.Hub_#0002) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 17/12/2016 4:55:56 AM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 17/12/2016 4:51:26 AM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 04/12/2016 11:41:05 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Error Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 14/01/2018 9:15:10 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 14/01/2018 7:53:55 PM
    Type: Error Category: 0
    Event: 5 Source: Microsoft-Windows-Kernel-General
    {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-21-3104806541-1533417482-1089993493-1002-01142018145355260-ntuser.dat' was corrupted and it has been recovered. Some data might have been lost.

    Log: 'System' Date/Time: 14/01/2018 1:46:12 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 13/01/2018 6:18:20 PM
    Type: Error Category: 2
    Event: 138 Source: Ntfs
    The transaction resource manager at C:\ encountered a fatal error and was shut down. The data contains the error code.

    Log: 'System' Date/Time: 13/01/2018 4:17:21 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 13/01/2018 4:13:48 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Superfetch service terminated with the following error: The service has not been started.

    Log: 'System' Date/Time: 13/01/2018 3:27:09 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 12/01/2018 10:55:45 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 12/01/2018 10:46:54 PM
    Type: Error Category: 0
    Event: 7000 Source: Service Control Manager
    The Garmin Device Interaction Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

    Log: 'System' Date/Time: 12/01/2018 10:46:54 PM
    Type: Error Category: 0
    Event: 7009 Source: Service Control Manager
    A timeout was reached (30000 milliseconds) while waiting for the Garmin Device Interaction Service service to connect.

    Log: 'System' Date/Time: 12/01/2018 9:31:28 PM
    Type: Error Category: 0
    Event: 5 Source: Microsoft-Windows-Kernel-General
    {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-21-3104806541-1533417482-1089993493-1002-01122018163127351-ntuser.dat' was corrupted and it has been recovered. Some data might have been lost.

    Log: 'System' Date/Time: 12/01/2018 8:11:43 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 12/01/2018 8:08:31 PM
    Type: Error Category: 0
    Event: 6008 Source: EventLog
    The previous system shutdown at 3:06:55 PM on ?1/?12/?2018 was unexpected.

    Log: 'System' Date/Time: 12/01/2018 6:06:23 PM
    Type: Error Category: 0
    Event: 10010 Source: Microsoft-Windows-DistributedCOM
    The server {ED1D0FDF-4414-470A-A56D-CFB68623FC58} did not register with DCOM within the required timeout.

    Log: 'System' Date/Time: 12/01/2018 4:15:49 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    Log: 'System' Date/Time: 12/01/2018 4:15:40 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    Log: 'System' Date/Time: 12/01/2018 4:15:32 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    Log: 'System' Date/Time: 12/01/2018 4:10:46 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    Log: 'System' Date/Time: 12/01/2018 4:10:38 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    Log: 'System' Date/Time: 12/01/2018 4:10:29 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Information Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 14/01/2018 10:16:47 PM
    Type: Information Category: 0
    Event: 7040 Source: Service Control Manager
    The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.

    Log: 'System' Date/Time: 14/01/2018 9:22:17 PM
    Type: Information Category: 0
    Event: 7045 Source: Service Control Manager
    A service was installed in the system. Service Name: MBAMWebProtection Service File Name: \SystemRoot\system32\DRIVERS\mwac.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:

    Log: 'System' Date/Time: 14/01/2018 9:16:46 PM
    Type: Information Category: 0
    Event: 7040 Source: Service Control Manager
    The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.

    Log: 'System' Date/Time: 14/01/2018 9:15:12 PM
    Type: Information Category: 0
    Event: 14206 Source: Microsoft-Windows-WMPNSS-Service
    Media server 'HP: [email protected]:' was successfully initialized and is sharing media with network media devices.

    Log: 'System' Date/Time: 14/01/2018 9:15:11 PM
    Type: Information Category: 0
    Event: 14204 Source: Microsoft-Windows-WMPNSS-Service
    Service 'WMPNetworkSvc' started.

    Log: 'System' Date/Time: 14/01/2018 9:13:32 PM
    Type: Information Category: 0
    Event: 6 Source: Microsoft-Windows-FilterManager
    File System Filter 'MBAMFarflt' (6.3, ?2017?-?09?-?05T18:44:07.000000000Z) has successfully loaded and registered with Filter Manager.

    Log: 'System' Date/Time: 14/01/2018 9:13:31 PM
    Type: Information Category: 0
    Event: 6 Source: Microsoft-Windows-FilterManager
    File System Filter 'MBAMProtection' (6.3, ?2017?-?10?-?12T10:23:13.000000000Z) has successfully loaded and registered with Filter Manager.

    Log: 'System' Date/Time: 14/01/2018 9:13:31 PM
    Type: Information Category: 0
    Event: 7045 Source: Service Control Manager
    A service was installed in the system. Service Name: MBAMProtection Service File Name: \SystemRoot\system32\DRIVERS\mbam.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:

    Log: 'System' Date/Time: 14/01/2018 9:13:28 PM
    Type: Information Category: 0
    Event: 7045 Source: Service Control Manager
    A service was installed in the system. Service Name: MBAMWebProtection Service File Name: \SystemRoot\system32\DRIVERS\mwac.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:

    Log: 'System' Date/Time: 14/01/2018 9:13:28 PM
    Type: Information Category: 0
    Event: 7045 Source: Service Control Manager
    A service was installed in the system. Service Name: MBAMFarflt Service File Name: \SystemRoot\system32\DRIVERS\farflt.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:

    Log: 'System' Date/Time: 14/01/2018 9:13:27 PM
    Type: Information Category: 0
    Event: 7045 Source: Service Control Manager
    A service was installed in the system. Service Name: MBAMSwissArmy Service File Name: \SystemRoot\system32\DRIVERS\mbamswissarmy.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:

    Log: 'System' Date/Time: 14/01/2018 9:13:00 PM
    Type: Information Category: 0
    Event: 7026 Source: Service Control Manager
    The following boot-start or system-start driver(s) did not load: dam EhStorClass

    Log: 'System' Date/Time: 14/01/2018 9:12:57 PM
    Type: Information Category: 1101
    Event: 7001 Source: Microsoft-Windows-Winlogon
    User Logon Notification for Customer Experience Improvement Program

    Log: 'System' Date/Time: 14/01/2018 9:12:56 PM
    Type: Information Category: 0
    Event: 10148 Source: Microsoft-Windows-WinRM
    The WinRM service is listening for WS-Management requests. User Action Use the following command to see the specific IPs on which WinRM is listening: winrm enumerate winrm/config/listener

    Log: 'System' Date/Time: 14/01/2018 9:12:55 PM
    Type: Information Category: 0
    Event: 5211 Source: Microsoft-Windows-WAS
    The Windows Process Activation Service (WAS) started with 'Classic' mode using 'ConfigurationSystem'

    Log: 'System' Date/Time: 14/01/2018 9:12:45 PM
    Type: Information Category: 0
    Event: 10001 Source: Microsoft-Windows-WLAN-AutoConfig
    WLAN Extensibility Module has successfully started. Module Path: C:\Windows\System32\IWMSSvc.dll

    Log: 'System' Date/Time: 14/01/2018 9:12:43 PM
    Type: Information Category: 0
    Event: 4000 Source: Microsoft-Windows-WLAN-AutoConfig
    WLAN AutoConfig service has successfully started.

    Log: 'System' Date/Time: 14/01/2018 9:12:43 PM
    Type: Information Category: 4
    Event: 51046 Source: Microsoft-Windows-DHCPv6-Client
    DHCPv6 client service is started

    Log: 'System' Date/Time: 14/01/2018 9:12:43 PM
    Type: Information Category: 4
    Event: 50036 Source: Microsoft-Windows-Dhcp-Client
    DHCPv4 client service is started

    Log: 'System' Date/Time: 14/01/2018 9:12:38 PM
    Type: Information Category: 0
    Event: 6 Source: Microsoft-Windows-FilterManager
    File System Filter 'luafv' (6.3, ?2017?-?10?-?10T11:36:39.000000000Z) has successfully loaded and registered with Filter Manager.
     
  7. dmccoy

    dmccoy

    Joined:
    Oct 7, 2017
    Messages:
    4,489
    First Name:
    Darrin
    I don’t see any errors with your event viewer but it was probaby recorded a lot earlier. Have you made sure thst .Net 3.5 is instslled and working correctly? Usually you delete the registry entry and it will be rebuilt on reboot. Have you tried that method?

    You have some errors with malwarebytes, I am not sure if it is still installed or not. If it is, then recommend uninstalling or reinstalling the latest version

    Also shows your driver is bad for your cd-rom so its needs updated.

    Another option to try is the following:
    Windows All in One Repair Tool
    https://www.bleepingcomputer.com/download/windows-repair-all-in-one/
    Download either the portable or install program

    1. Start computer in Safe Mode
    2. Disable any Anti-Virus programs
    3. Start the program
    4. When program first starts it will run quick file check
    5. Click on the X button after the scan shows Done!
    6. Click on Settings tab and Select Check for Updates
    7. Click on Pre-Repair Steps Tab and Run All 4 Steps
    8. Select both Registry Backup and Create System Restore
    9. Click Presets: All Repairs
    10. Click Start Repairs

    For Best Results Run the Repairs option Twice!
     
  8. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    Thank you.

    I had no problems until I did the Windows roll-up updates (I recall there were 6-7) on 1-9-18, so if there was something recorded a lot earlier, I never noticed it. Since I view Event Viewer a lot, especially after doing updates or installing software, I know that it disappeared after I did the Windows updates (including Spectre and Meltdown fixes) on the 9th. Since then, I have been unable to view Event Viewer and I get the MMC snap-in error message I mentioned in my first post.

    No, don't know if .NET 3.5 is installed and working correctly. How do I check this? I haven't done anything with the registry. Frankly, without instruction, I don't go in there at all. :(

    Yes, Malwarebytes is still installed. I will try the uninstall/reinstall.

    I've had no problems with my CD-ROM. I thought the problem was with the disc in the CD-ROM, no? I did have a bad disc that wouldn't play, but you say it's the driver? Please tell me how I can update the driver?

    You said ANOTHER option to try ... do you mean to try this All-In-One tool instead of the other things??? Or should I try the other option after doing the Malwarebytes reinstall and CD-ROM driver fix?

    As I said, I'm not very computer savvy, so if I seem cautious, it's because I don't want to mess things up. I'm grateful for your kind assistance. :)

    nigebirch
     
  9. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    I uninstalled Malwarebytes and reinstalled it. Ran a scan which came back clean.
    I checked my CD-ROM driver, and it is up-t0-date. I ran another VEW scan, and the log showed no CD-ROM events this time. Neither were there any Malwarebytes events.

    Still no Event Viewer snap-in.

    Once I hear from you how to check .NET 3.5, I will do this. Then, I guess I can try the Windows All In One Repair Tool?

    Thanx,

    nigebirch
     
  10. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    Just searched the registry for NET Framework, and, yes, >NET 3.5 is installed. Is it working correctly? I don't know how to tell.
    Thanx,
    NB
     
  11. dmccoy

    dmccoy

    Joined:
    Oct 7, 2017
    Messages:
    4,489
    First Name:
    Darrin
    Okay, good to hear the logs are cleaned. To check for .Net 3.5

    Go into Control panel and under Programs and Features.
    Select Turn Windows fratures on and off
    Check .Net 3.5. Is selected or not
    If already checked, then uncheck restart and then perform steps again and Check .Net 3.5 to reinstall

    If those steps don’t get us anywhere then go ahead and run the All in one repair tool and let me know if it helps or not.

    The next step would be a repair install as I mentioned in post 2 with link for steps.
     
  12. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    My .NET 3.5 is listed in the registry, and it is ticked in Control Panel. I have a .NET 3.5 update

    pending in Windows Updates, but I have NOT installed it because it was one of the several updates done

    on 1/9/18, one or more of which caused the problem I am having with my PC now: No Event Viewer and unrepairable component store corruption.




    Running DISM late last night, here is what was reported:

    DISM RestoreHealth command:

    The restore operation failed. Either the repair source was not found or the component store cannot be

    repaired.

    Error: 0x800f081f

    DISM failed. No operation was performed.
    For more information, review the log file.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    *************

    In checking DISM log, here is what I found to be irreparable according to the log:

    Checking System Update Readiness.

    (p) CSI Payload Corrupt amd64_microsoft-windows-ie-

    ratings_31bf3856ad364e35_11.0.9600.17278_none_cb6116c93fa8fd17\icrav03.rat
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt amd64_microsoft-windows-ie-

    ratings_31bf3856ad364e35_11.0.9600.18378_none_cb5648c33fb1162f\icrav03.rat
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt amd64_microsoft-windows-ie-

    ratings_31bf3856ad364e35_11.0.9600.17498_none_cb4d77853fb767a7\icrav03.rat
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt amd64_microsoft-windows-ie-

    ratings_31bf3856ad364e35_11.0.9600.17239_none_cb5cfed93facb15c\icrav03.rat
    Repair failed: Missing replacement payload.

    Summary:
    Operation: Detect and Repair
    Operation result: 0x0
    Last Successful Step: Entire operation completes.
    Total Detected Corruption: 4
    CBS Manifest Corruption: 0
    CBS Metadata Corruption: 0
    CSI Manifest Corruption: 0
    CSI Metadata Corruption: 0
    CSI Payload Corruption: 4
    Total Repaired Corruption: 0
    CBS Manifest Repaired: 0
    CSI Manifest Repaired: 0
    CSI Payload Repaired: 0
    CSI Store Metadata refreshed: True

    Total Operation Time: 315 seconds.
    *******************************

    Finally, last night, I ran this Admin command after the DISM RestoreHealth did not work:

    Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

    Here's what was reported. I have no idea what this means:

    Component Stre (WinSxS) information:

    Windows Explorer Reported Size of Component Store : 11.44 GB

    Actual Size of Component Store : 11.04 GB

    Shared with Windows : 5.04 GM
    Backups and Disabled Features : 3.18 GB
    Cache and Temporary Data : 2.81 GB

    Date of Last Cleanup : 2018-01-06 12:24:39

    Number of Reclaimable Packages : 19
    Component Store Cleanup Recommended : Yes

    The operation completed successfully.
    *******************************
    Here's the latest VEW.exe log just done. Why it's showing MBAM problems after removal and

    reinstallation with no problems following reinstallation, I have no clue:

    Vino's Event Viewer v01c run on Windows 7 in English
    Report run at 15/01/2018 4:44:40 PM

    Note: All dates below are in the format dd/mm/yyyy

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Critical Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 12/01/2018 8:08:18 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 16/12/2017 6:00:35 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 15/09/2017 6:56:58 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 25/07/2017 2:34:17 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 07/07/2017 11:57:37 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 07/07/2017 11:36:42 PM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.

    This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 07/07/2017 12:10:00 AM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 23/06/2017 2:31:53 PM
    Type: Critical Category: 64
    Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Apple iPod (location Port_#0004.Hub_#0002) is offline due to a user-mode driver crash.

    Windows will attempt to restart the device in the shared process 1 more times before moving the device

    in its own process. Please contact the device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 23/06/2017 2:31:53 PM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.

    This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 07/05/2017 2:25:42 PM
    Type: Critical Category: 64
    Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Apple iPod (location Port_#0004.Hub_#0002) is offline due to a user-mode driver crash.

    Windows will attempt to restart the device in the shared process 1 more times before moving the device

    in its own process. Please contact the device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 07/05/2017 2:25:42 PM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.

    This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 02/05/2017 3:38:22 PM
    Type: Critical Category: 64
    Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Apple iPod (location Port_#0002.Hub_#0002) is offline due to a user-mode driver crash.

    Windows will attempt to restart the device in the shared process 1 more times before moving the device

    in its own process. Please contact the device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 02/05/2017 3:38:22 PM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.

    This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 19/12/2016 3:12:41 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 17/12/2016 4:58:12 AM
    Type: Critical Category: 64
    Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Validity Sensors (WBF) (PID=0050) (location Port_#0014.Hub_#0002) is offline due to a

    user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the

    device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 17/12/2016 4:58:12 AM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.

    This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 17/12/2016 4:55:56 AM
    Type: Critical Category: 64
    Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
    The device Validity Sensors (WBF) (PID=0050) (location Port_#0014.Hub_#0002) is offline due to a

    user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the

    device manufacturer for more information about this problem.

    Log: 'System' Date/Time: 17/12/2016 4:55:56 AM
    Type: Critical Category: 64
    Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
    A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.

    This may temporarily interrupt your ability to access the devices.

    Log: 'System' Date/Time: 17/12/2016 4:51:26 AM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 04/12/2016 11:41:05 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system

    stopped responding, crashed, or lost power unexpectedly.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Error Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 15/01/2018 2:08:23 AM
    Type: Error Category: 0
    Event: 5 Source: Microsoft-Windows-Kernel-General
    {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-21

    -3104806541-1533417482-1089993493-1002-01142018210823053-ntuser.dat' was corrupted and it has been

    recovered. Some data might have been lost.

    Log: 'System' Date/Time: 15/01/2018 2:04:10 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 14/01/2018 11:06:53 PM
    Type: Error Category: 0
    Event: 5 Source: Microsoft-Windows-Kernel-General
    {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-21

    -3104806541-1533417482-1089993493-1002-01142018180653362-ntuser.dat' was corrupted and it has been

    recovered. Some data might have been lost.

    Log: 'System' Date/Time: 14/01/2018 9:15:10 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 14/01/2018 7:53:55 PM
    Type: Error Category: 0
    Event: 5 Source: Microsoft-Windows-Kernel-General
    {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-21

    -3104806541-1533417482-1089993493-1002-01142018145355260-ntuser.dat' was corrupted and it has been

    recovered. Some data might have been lost.

    Log: 'System' Date/Time: 14/01/2018 1:46:12 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 13/01/2018 6:18:20 PM
    Type: Error Category: 2
    Event: 138 Source: Ntfs
    The transaction resource manager at C:\ encountered a fatal error and was shut down. The data

    contains the error code.

    Log: 'System' Date/Time: 13/01/2018 4:17:21 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 13/01/2018 4:13:48 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Superfetch service terminated with the following error: The service has not been started.

    Log: 'System' Date/Time: 13/01/2018 3:27:09 AM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 12/01/2018 10:55:45 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 12/01/2018 10:46:54 PM
    Type: Error Category: 0
    Event: 7000 Source: Service Control Manager
    The Garmin Device Interaction Service service failed to start due to the following error: The service

    did not respond to the start or control request in a timely fashion.

    Log: 'System' Date/Time: 12/01/2018 10:46:54 PM
    Type: Error Category: 0
    Event: 7009 Source: Service Control Manager
    A timeout was reached (30000 milliseconds) while waiting for the Garmin Device Interaction Service

    service to connect.

    Log: 'System' Date/Time: 12/01/2018 9:31:28 PM
    Type: Error Category: 0
    Event: 5 Source: Microsoft-Windows-Kernel-General
    {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-21

    -3104806541-1533417482-1089993493-1002-01122018163127351-ntuser.dat' was corrupted and it has been

    recovered. Some data might have been lost.

    Log: 'System' Date/Time: 12/01/2018 8:11:43 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Interactive Services Detection service terminated with the following error: Incorrect function.

    Log: 'System' Date/Time: 12/01/2018 8:08:31 PM
    Type: Error Category: 0
    Event: 6008 Source: EventLog
    The previous system shutdown at 3:06:55 PM on ?1/?12/?2018 was unexpected.

    Log: 'System' Date/Time: 12/01/2018 6:06:23 PM
    Type: Error Category: 0
    Event: 10010 Source: Microsoft-Windows-DistributedCOM
    The server {ED1D0FDF-4414-470A-A56D-CFB68623FC58} did not register with DCOM within the required

    timeout.

    Log: 'System' Date/Time: 12/01/2018 4:15:49 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    Log: 'System' Date/Time: 12/01/2018 4:15:40 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    Log: 'System' Date/Time: 12/01/2018 4:15:32 AM
    Type: Error Category: 0
    Event: 7 Source: cdrom
    The device, \Device\CdRom0, has a bad block.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Warning Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 15/01/2018 4:36:30 AM
    Type: Warning Category: 0
    Event: 264 Source: Win32k
    A multi-touch device reported inconsistent contact information.

    Log: 'System' Date/Time: 15/01/2018 2:01:33 AM
    Type: Warning Category: 0
    Event: 264 Source: Win32k
    A multi-touch device reported inconsistent contact information.

    Log: 'System' Date/Time: 15/01/2018 2:01:27 AM
    Type: Warning Category: 212
    Event: 219 Source: Microsoft-Windows-Kernel-PnP
    The driver \Driver\WUDFRd failed to load for the device USB\VID_138A&PID_0050\e91100a17ced.

    Log: 'System' Date/Time: 15/01/2018 1:59:33 AM
    Type: Warning Category: 0
    Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
    WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\IWMSSvc.dll

    Log: 'System' Date/Time: 14/01/2018 9:12:37 PM
    Type: Warning Category: 0
    Event: 264 Source: Win32k
    A multi-touch device reported inconsistent contact information.

    Log: 'System' Date/Time: 14/01/2018 9:12:32 PM
    Type: Warning Category: 212
    Event: 219 Source: Microsoft-Windows-Kernel-PnP
    The driver \Driver\WUDFRd failed to load for the device USB\VID_138A&PID_0050\e91100a17ced.

    Log: 'System' Date/Time: 14/01/2018 9:11:00 PM
    Type: Warning Category: 0
    Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
    WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\IWMSSvc.dll

    Log: 'System' Date/Time: 14/01/2018 2:32:31 AM
    Type: Warning Category: 0
    Event: 264 Source: Win32k
    A multi-touch device reported inconsistent contact information.

    Log: 'System' Date/Time: 14/01/2018 1:42:59 AM
    Type: Warning Category: 0
    Event: 264 Source: Win32k
    A multi-touch device reported inconsistent contact information.

    Log: 'System' Date/Time: 14/01/2018 1:42:47 AM
    Type: Warning Category: 212
    Event: 219 Source: Microsoft-Windows-Kernel-PnP
    The driver \Driver\WUDFRd failed to load for the device USB\VID_138A&PID_0050\e91100a17ced.

    Log: 'System' Date/Time: 14/01/2018 1:42:07 AM
    Type: Warning Category: 0
    Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
    WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\IWMSSvc.dll

    Log: 'System' Date/Time: 14/01/2018 1:30:25 AM
    Type: Warning Category: 0
    Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
    WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\IWMSSvc.dll

    Log: 'System' Date/Time: 13/01/2018 6:18:20 PM
    Type: Warning Category: 2
    Event: 134 Source: Ntfs
    The transaction resource manager on volume C: encountered an error during recovery. The resource

    manager will continue recovery.

    Log: 'System' Date/Time: 13/01/2018 6:18:20 PM
    Type: Warning Category: 2
    Event: 134 Source: Ntfs
    The transaction resource manager on volume C: encountered an error during recovery. The resource

    manager will continue recovery.

    Log: 'System' Date/Time: 13/01/2018 6:08:57 PM
    Type: Warning Category: 0
    Event: 153 Source: disk
    The IO operation at logical block address 0x0 for Disk 2 (PDO name: \Device\00000089) was retried.

    Log: 'System' Date/Time: 13/01/2018 3:05:21 PM
    Type: Warning Category: 0
    Event: 153 Source: disk
    The IO operation at logical block address 0x0 for Disk 2 (PDO name: \Device\00000083) was retried.

    Log: 'System' Date/Time: 13/01/2018 2:59:49 PM
    Type: Warning Category: 0
    Event: 153 Source: disk
    The IO operation at logical block address 0x0 for Disk 2 (PDO name: \Device\0000007f) was retried.

    Log: 'System' Date/Time: 13/01/2018 4:47:01 AM
    Type: Warning Category: 0
    Event: 264 Source: Win32k
    A multi-touch device reported inconsistent contact information.

    Log: 'System' Date/Time: 13/01/2018 4:14:30 AM
    Type: Warning Category: 0
    Event: 264 Source: Win32k
    A multi-touch device reported inconsistent contact information.

    Log: 'System' Date/Time: 13/01/2018 4:14:22 AM
    Type: Warning Category: 212
    Event: 219 Source: Microsoft-Windows-Kernel-PnP
    The driver \Driver\WUDFRd failed to load for the device USB\VID_138A&PID_0050\e91100a17ced.

    (Just noticed your name. My first name is Dorrin.)
     
  13. dmccoy

    dmccoy

    Joined:
    Oct 7, 2017
    Messages:
    4,489
    First Name:
    Darrin
    So where are we at after all your repair attempts?

    Did you try uninstalling and reinstalling .Net 3.5. Either the repair install or All in one repair fixed the event viewer or .Net?

    Okay so have you ran Dism command after running the Analyze and fix?

    The Malwarebytes errors look like old corrupted registry entries and it said they were fixed.
     
  14. nigebirch

    nigebirch Thread Starter

    Joined:
    Jan 13, 2018
    Messages:
    33
    Yes, it said Malwarebytes errors were fixed. Now, apparently not.
    No, I didn't uninstall .NET 3.5 and reinstall. Why? Because I read online that when some people who were having problems like mine did this, they were not able to reinstall .NET 3.5 and this made problems worse. Is this not a possibility?
    I ran DISM command that said component store corruptions could not be fixed. I rant the Analyze in hopes of getting some more information to bring back here. I don't understand what the Analyze log reported, so I brought it here for you, hoping it would help. ;)

    I did not run any fix. Are you referring to the Repair file you linked in another post? Is this what you suggest at this point? I want to be sure because I am afraid of losing my installed applications that have to be repurchased if lost. Sorry for being Ms. Paranoid, but could the component store items that cannot be fixed be causing all these problems? Did you see the four component store errors I posted????

    Thanx
     
  15. dmccoy

    dmccoy

    Joined:
    Oct 7, 2017
    Messages:
    4,489
    First Name:
    Darrin
    First, I would recommend creating a disk image backup so if any issues then you can easily restore your system to the way it was.

    https://www.macrium.com/reflectfree

    We aren,t sure if Malwarebytes was fixed or not since you havenkt provide nee logs.

    Yes, i would recommend uninstalling and reinstalling .Net3.5

    It looked like you performed the store component repair from the message below. Please confirm weather you selected yes or not.

    Number of Reclaimable Packages : 19
    Component Store Cleanup Recommended : Yes
     
  16. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1202885

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice