Did in-place upgrade from Windows 7 to 10. Now constant timeouts, errors, unusable

[neosapien]

So I had been running Windows 7 on this system (same installation, clean installed once shortly after Win 7 launch and stayed with that since then) ever since it came out, and yesterday I made a system image to back up, then upgraded from 7 to 10. In-place upgrade, not a clean install.

When the install first completed, it booted up into a temporary user account, and I freaked out to find that my desktop was empty. Then I restarted the PC, and it correctly loaded my user account, and all my files were back on the desktop. Phew. Then I hibernated the machine and went to bed.

Now my system behaves like it has a hangover. Constant timeouts, in Event Viewer, 7000 and 7009 errors.

I think that my in-place upgrade may have just worked poorly and resulted in an unstable system. I've got like 7 years worth of programs that I would have to reinstall, which would take forever, so of course I wanted to do an in-place upgrade over a clean install. But with how crappily my system is performing now, I'm getting the impression that a clean install might be my only recourse, though I hope not.

As far as I can see, I have two options:

1) Restore from system image to Windows 7 installation. Which would kinda suck now that I've put all this effort into upgrading to Windows 10.
2) Do a clean install, and reinstall every program I've installed since 2009 and still need. Is there a process that would make this easier?
3) Maybe someone has some other ideas?

 

[RampantAndroid]

sfc /scannow, run windows update, make sure you've got all the drivers installed. Those errors are services timing out. What services?

Otherwise...well, I feel like a machine could use a clean install every so often...

 

[nerp]

I'd just reinstall Windows 10 fresh and then install your old apps over time, as you need them. Space out the misery. No need to waste a whole weekend. It's also an opportunity to re-think stuff you install out of habit or just because when in reality you use rarely, if ever. In fact, many programs people use are old and they stick with them because they paid for them or wathever but there are better options out there, sometimes included in the OS or free. It's also a chance to abandon whatever antivirus/spyware tools you run since they are all utterly pointless, ineffective and worthless.

 

[Elixer]

7 years of stuff is a long time and lots and lots of registry tinkering going on there.
You could try a 'reset' of windows 10, and it will tell you if you want to keep the programs or not.
Obviously, there are most likely some programs that will puke on 10, and I don't think you still use all those, let alone half, so, I would just do a clean install, and install what you need.

 

[neosapien]

Okay, I think I've narrowed it down. The system basically stops working after I resume from either a hibernate or a sleep, and it's just constant timeouts.

This is what happens when I try to run sfc /scannow, and my Windows Logs > System from immediately before putting the PC to sleep mode, and then after resuming from sleep mode. It's in descending order, so the events start chronologically at the bottom and then work their way up.

C:\WINDOWS\system32>sfc /scannow
Windows Resource Protection could not start the repair service.

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          4/8/2016 2:21:52 AM
Event ID:      10005
Task Category: None
Level:         Error
Keywords:      Classic
User:          neosapien-PC\neosapien
Computer:      neosapien-PC
Description:
DCOM got error "1053" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{8F5DF053-3013-4DD8-B5F4-88214E81C0CF}


Log Name:      System
Source:        Service Control Manager
Date:          4/8/2016 2:21:52 AM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
The Windows Modules Installer 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 Name:      System
Source:        Service Control Manager
Date:          4/8/2016 2:21:52 AM
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
A timeout was reached (30000 milliseconds) while waiting for the Windows Modules Installer service to connect.

Log Name:      System
Source:        Service Control Manager
Date:          4/8/2016 2:21:30 AM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
The Adobe Flash Player Update 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 Name:      System
Source:        Service Control Manager
Date:          4/8/2016 2:21:30 AM
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
A timeout was reached (30000 milliseconds) while waiting for the Adobe Flash Player Update Service service to connect.

Log Name:      System
Source:        Service Control Manager
Date:          4/8/2016 2:10:21 AM
Event ID:      7011
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

Log Name:      System
Source:        storahci
Date:          4/8/2016 2:09:26 AM
Event ID:      129
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
Reset to device, \Device\RaidPort0, was issued.

Log Name:      System
Source:        e1iexpress
Date:          4/8/2016 2:09:18 AM
Event ID:      32
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
Intel(R) 82579V Gigabit Network Connection
 Network link has been established at 1Gbps full duplex.

Log Name:      System
Source:        BTHUSB
Date:          4/8/2016 2:09:16 AM
Event ID:      18
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup.

Log Name:      System
Source:        mv91xx
Date:          4/8/2016 2:09:16 AM
Event ID:      17
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
Adapter is detected.

Log Name:      System
Source:        Microsoft-Windows-Power-Troubleshooter
Date:          4/8/2016 2:09:16 AM
Event ID:      1
Task Category: None
Level:         Information
Keywords:      
User:          LOCAL SERVICE
Computer:      neosapien-PC
Description:
The system has returned from a low power state.
Sleep Time: ‎2016‎-‎04‎-‎08T05:58:57.147908700Z
Wake Time: ‎2016‎-‎04‎-‎08T06:09:16.346854000Z
Wake Source: Power Button

Log Name:      System
Source:        e1iexpress
Date:          4/8/2016 2:09:15 AM
Event ID:      27
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
Intel(R) 82579V Gigabit Network Connection
 Network link is disconnected.

Log Name:      System
Source:        Microsoft-Windows-Kernel-General
Date:          4/8/2016 2:09:15 AM
Event ID:      1
Task Category: None
Level:         Information
Keywords:      Time
User:          N/A
Computer:      neosapien-PC
Description:
The system time has changed to ‎2016‎-‎04‎-‎08T06:09:15.500000000Z from ‎2016‎-‎04‎-‎08T05:59:04.392666900Z.
Change Reason: System time synchronized with the hardware clock.

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          4/8/2016 1:59:04 AM
Event ID:      137
Task Category: None
Level:         Error
Keywords:      (4)
User:          N/A
Computer:      neosapien-PC
Description:
The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance.

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          4/8/2016 1:59:04 AM
Event ID:      107
Task Category: (102)
Level:         Information
Keywords:      (70368744177664),(64),(4)
User:          N/A
Computer:      neosapien-PC
Description:
The system has resumed from sleep.

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          4/8/2016 1:58:58 AM
Event ID:      42
Task Category: (64)
Level:         Information
Keywords:      (70368744177664),(4)
User:          N/A
Computer:      neosapien-PC
Description:
The system is entering sleep.
Sleep Reason: Application API

 

[abekl]

I have had alot of experience with issues similar to yours. I've never found a good solution to fixing service timeouts, other that reinstalling the OS.

 

[RampantAndroid]

So you ran sfc after rebooting, before it had ever hibernated?

Have you tried running it from safe mode?

 

[Ketchup]

I did a recent upgrade myself and found that some programs didn't make the transition well. Sure, Windows 10 told me about a couple of them, but there were a few more. I think that is what the trustedinstaller failure is trying to telling you. Look and see if you can find what program it is referring to, then uninstall/reinstall.

If event viewer isn't forthcoming enough, you may have to go down through programs and see what is working/what isn't. Before you do that, make sure Windows Update isn't in the middle of trying to install something.

Tip: after checking WU, start with programs that run in the background (such as Antivirus and sound software).

 

[SimMike2]

As with any upgrade like this, I always make a complete image of my boot drive before starting.

 

[neosapien]

I narrowed it down some more. A clean install of Windows 10 doesn't result in the same timeout issues I experience with the upgrade install.

@RampantAndroid
sfc /scannow works fine after rebooting, but when Windows 10 goes crazy after I sleep or hibernate, it doesn't work anymore until the next reboot.

@SimMike2
Same here

@Ketchup
It actually seemed more random, like Windows had just gone crazy and everything I tried to do resulted in an error.

 

[mikeymikec]

Log Name: System
Source: storahci
Date: 4/8/2016 2:09:26 AM
Event ID: 129
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: neosapien-PC
Description:
Reset to device, \Device\RaidPort0, was issued.

That's the serious one. AHCI drivers perhaps? It looks like you're using the default driver but I'm not certain.

I would also check SMART stats for the drive (just in case).

 

[neosapien]

That's the serious one. AHCI drivers perhaps? It looks like you're using the default driver but I'm not certain.

I would also check SMART stats for the drive (just in case).

I'm using the "Intel(R) 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller - 1C02" AHCI driver. Here's the SMART stats on the drive: (I'm not using Win8, my CrystalDiskInfo is just old)

----------------------------------------------------------------------------
CrystalDiskInfo 5.6.1 (C) 2008-2013 hiyohiyo
                                Crystal Dew World : http://crystalmark.info/
----------------------------------------------------------------------------

    OS : Windows 8  [6.2 Build 9200] (x64)
  Date : 2016/04/09 5:13:25

-- Controller Map ----------------------------------------------------------
 + Intel(R) 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller - 1C02 [ATA]
   - Samsung SSD 850 EVO 1TB
   - WDC WD2001FASS-00W2B0
   - WDC WD7500AACS-00D6B1
   - WDC WD10EADS-00L5B1
   - HL-DT-ST BD-RE  WH10LS30
 - Microsoft Storage Spaces Controller [SCSI]
 - Marvell 91xx SATA 6G Controller [SCSI]
 - JMicron JMB36X Controller [SCSI]

-- Disk List ---------------------------------------------------------------
 (1) Samsung SSD 850 EVO 1TB : 1000.2 GB [0/1/0, pd1] - sg
 (2) WDC WD2001FASS-00W2B0 : 2000.3 GB [1/1/0, pd1] - wd
 (3) WDC WD7500AACS-00D6B1 : 750.1 GB [2/1/0, pd1] - wd
 (4) WDC WD10EADS-00L5B1 : 1000.2 GB [3/1/0, pd1] - wd
 (5) SanDisk SDSSDX480GG25 : 480.1 GB [5/0/0, sa1] - sf

----------------------------------------------------------------------------
 (1) Samsung SSD 850 EVO 1TB
----------------------------------------------------------------------------
           Model : Samsung SSD 850 EVO 1TB
        Firmware : EMT02B6Q
   Serial Number : 
       Disk Size : 1000.2 GB (8.4/137.4/1000.2/1000.2)
     Buffer Size : Unknown
     Queue Depth : 32
    # of Sectors : 1953525168
   Rotation Rate : ---- (SSD)
       Interface : Serial ATA
   Major Version : ACS-2
   Minor Version : ATA8-ACS version 4c
   Transfer Mode : SATA/600
  Power On Hours : 595 hours
  Power On Count : 41 count
     Host Writes : 1417 GB
Wear Level Count : 1
     Temparature : 34 C (93 F)
   Health Status : Good (100 %)
        Features : S.M.A.R.T., 48bit LBA, NCQ, TRIM
       APM Level : ----
       AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
05 100 100 _10 000000000000 Reallocated Sector Count
09 _99 _99 __0 000000000253 Power-on Hours
0C _99 _99 __0 000000000029 Power-on Count
B1 _99 _99 __0 000000000001 Wear Leveling Count
B3 100 100 _10 000000000000 Used Reserved Block Count (Total)
B5 100 100 _10 000000000000 Program Fail Count (Total)
B6 100 100 _10 000000000000 Erase Fail Count (Total)
B7 100 100 _10 000000000000 Runtime Bad Block (Total)
BB 100 100 __0 000000000000 Uncorrectable Error Count
BE _66 _63 __0 000000000022 Airflow Temperature
C3 200 200 __0 000000000000 ECC Error Rate
C7 _99 _99 __0 000000000001 CRC Error Count
EB 100 100 __0 000000000000 POR Recovery Count
F1 _99 _99 __0 0000B120D36D Total LBA Written

 

[mikeymikec]

The SMART stats look OK at a glance, but I'm not used to reading the raw values (though the notable ones seem to say zero).

Did you update the AHCI driver after the upgrade? I suspect that all you're seeing there is the controller name being changed (as a result of running the Intel chipset utility on Win7?), though it is still using the generic Windows AHCI driver (storahci) I think. The Intel AHCI driver service is normally called iaStor.

IMO, install the latest version of Intel Rapid Storage Technology for Windows 10, and if it thinks your hardware is too old for it then you might need to hunt down a specific version that suits your chipset (maybe the Asus site has one for Win10, but I doubt it). I'd go with a driver over the Intel site rather than Asus personally.

I wonder whether I'd first run a recent version of the Intel Chipset utility as that does update smbus drivers (and maybe a few other obscure bits? dunno), as well as the Intel Management Engine Interface drivers.

The reason why I'm pointing the finger at AHCI is that you've got a load of service hangs right across the board including third party software like Adobe's service), and you've got an AHCI timeout, it stands to reason to me that they have a common cause, ie. disk I/O is not 100% right for some reason.

I'd probably also update any other drivers as well, but I'd start with the core stuff.

 

[neosapien]

Okay, I tried installing the latest Intel RST, and it said my platform wasn't supported. I looked up info on my chipset and found that for Intel 6-series chipsets like my P67, the latest one to use is apparently 12.9.4.1000, dated 04/24/2014, so I installed that. Asus's website has one for Windows 8.1 x64, that's the latest they have, it's like 12.8 or something.

I ran the Intel Driver Update Utility, which recommended that I install the latest Intel Chipset Device Software (INF Update Utility-EXE Only), latest version 10.1.1.14, my installed version, 10.0.10586.0. I downloaded and then installed, rebooted, reran the Intel Driver Update Utility again, and it still said the same thing, so it seems oblivious to me having installed its recommended driver. Not sure why that is. Then when I go to Device Manager and look up the details of my Intel P67 Express Chipset Family LPC Interface Controller - 1C46, it says its driver version is actually 10.1.1.14, along with a few other Intel drivers that read as 10.1.1.14. So that's odd.

I installed Intel MEI Driver v11.0.3.1184.

Sadly, the problem of poor performance and extremely long timeouts after sleeping/hibernating the system persists. I tried disabling write caching on my main drive the 1TB Samsung SSD. This didn't solve the problem. Then I tried disabling link power management from within the Intel Rapid Storage Technology tool, also no effect.

 

[mikeymikec]

Sorry to hear that. Are the AHCI timeouts still occurring? Another thing I'd do is a full chkdsk (/f /v /r) on the system volume, but I don't think that fits with the symptoms. However, if there's file system oddness going on, that might explain why sfc didn't work (and fix that problem).

I don't think anyone has suggested dism /online /cleanup-image /restorehealth, so that's worth a shot.

Also, are the errors in the event log still as varied as before?

 

[Ketchup]

Since Asus doesn't officially support or have Windows 10 drivers for your board, I suspect your issues are from at least one of the drivers.

Device manager is your friend here. See what devices are marked Unknown. You can usually Google the Value in the Details tab and you are probably going to see what it is. Then you can see if there is a good Windows 10 driver for that device.

Looks like you also might want to do an uninstall/reinstall of Flash.

 

[neosapien]

Sorry to hear that. Are the AHCI timeouts still occurring? Another thing I'd do is a full chkdsk (/f /v /r) on the system volume, but I don't think that fits with the symptoms. However, if there's file system oddness going on, that might explain why sfc didn't work (and fix that problem).

I don't think anyone has suggested dism /online /cleanup-image /restorehealth, so that's worth a shot.

Also, are the errors in the event log still as varied as before?

The last AHCI timeout occurred on 4/8 at 2am, the one I posted here, none since then.

The errors I consistently get are:

Log Name:      System
Source:        Service Control Manager
Date:          4/9/2016 3:47:59 PM
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) Common Connectivity Framework service to connect.

Log Name:      System
Source:        Service Control Manager
Date:          4/9/2016 3:47:59 PM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
The Intel(R) Common Connectivity Framework 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 Name:      System
Source:        Service Control Manager
Date:          4/9/2016 3:45:49 PM
Event ID:      7001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      neosapien-PC
Description:
The NetTcpActivator service depends on the NetTcpPortSharing service which failed to start because of the following error: 
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Chkdsk results:

C:\WINDOWS\system32>chkdsk /f /v /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

C:\WINDOWS\system32>


Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
Cleaning up instance tags for file 0x509.
  666112 file records processed.                                                         File verification completed.
  6596 large file records processed.                                      0 bad file records processed.                                      
Stage 2: Examining file name linkage ...
  843992 index entries processed.                                                        Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered to lost and found.                     
Stage 3: Examining security descriptors ...
Cleaning up 1501 unused index entries from index $SII of file 0x9.
Cleaning up 1501 unused index entries from index $SDH of file 0x9.
Cleaning up 1501 unused security descriptors.
Security descriptor verification completed.
  88941 data files processed.                                            CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  666096 files processed.                                                                File data verification completed.

Stage 5: Looking for bad, free clusters ...
  136663185 free clusters processed.                                                        Free space verification is complete.

Windows has made corrections to the file system.
No further action is required.

 878623444 KB total disk space.
 330862928 KB in 541581 files.
    344628 KB in 88942 indexes.
         0 KB in bad sectors.
    763148 KB in use by the system.
     65536 KB occupied by the log file.
 546652740 KB available on disk.

      4096 bytes in each allocation unit.
 219655861 total allocation units on disk.
 136663185 allocation units available on disk.

Internal Info:
00 2a 0a 00 05 9f 09 00 2f 85 11 00 00 00 00 00  .*....../.......
a2 54 00 00 6d 00 00 00 00 00 00 00 00 00 00 00  .T..m...........

Windows has finished checking your disk.
Please wait while your computer restarts.

Ran dism:

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

Ran sfc again:

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Since Asus doesn't officially support or have Windows 10 drivers for your board, I suspect your issues are from at least one of the drivers.

Device manager is your friend here. See what devices are marked Unknown. You can usually Google the Value in the Details tab and you are probably going to see what it is. Then you can see if there is a good Windows 10 driver for that device.

Looks like you also might want to do an uninstall/reinstall of Flash.

I have two drivers, both for my Logitech G15 keyboard's display panel, that don't want to install (they just stay listed as Unknown device), Windows SideShow Driver for Logitech QVGA / Monochromoe devices, they just stay listed as Unknown device even after installing the latest Logitech Gaming Software. But they're not necessary for the keyboard to function, so I can just leave them disabled in Device Manager (right-click, disable).

I reinstalled flash.

Sadly, the issue of an unresponsive system with lots of timeouts still persists after sleep/hibernation.

 

[Ketchup]

Well you have three options:

1. Roll back to 7: I have used this on my system and it worked well.
2. Keep looking for fixes: you are pretty far into this one time-wise, so I don't know how much more you want to give it.
3. Backup and do a fresh install. Most time consuming, but considering you haven't gotten anywhere since starting the thread two days ago (and who knows how many days before that) you might want to just bite the bullet and do it instead of wasting more time.

I do have one suggestion before you go with 3. If you have an extra hard drive, install Windows 10 on that and see if you can get all drivers installed and all devices working before wiping your entire system for the main install.

 

[escrow4]

Okay, I tried installing the latest Intel RST, and it said my platform wasn't supported. I looked up info on my chipset and found that for Intel 6-series chipsets like my P67, the latest one to use is apparently 12.9.4.1000, dated 04/24/2014, so I installed that. Asus's website has one for Windows 8.1 x64, that's the latest they have, it's like 12.8 or something.

I ran the Intel Driver Update Utility, which recommended that I install the latest Intel Chipset Device Software (INF Update Utility-EXE Only), latest version 10.1.1.14, my installed version, 10.0.10586.0. I downloaded and then installed, rebooted, reran the Intel Driver Update Utility again, and it still said the same thing, so it seems oblivious to me having installed its recommended driver. Not sure why that is. Then when I go to Device Manager and look up the details of my Intel P67 Express Chipset Family LPC Interface Controller - 1C46, it says its driver version is actually 10.1.1.14, along with a few other Intel drivers that read as 10.1.1.14. So that's odd.

I installed Intel MEI Driver v11.0.3.1184.

Sadly, the problem of poor performance and extremely long timeouts after sleeping/hibernating the system persists. I tried disabling write caching on my main drive the 1TB Samsung SSD. This didn't solve the problem. Then I tried disabling link power management from within the Intel Rapid Storage Technology tool, also no effect.

Drivers have gotten lost. Clean install 10 and run Windows Update and let it choose the drivers.