Windows 10: Moved W10 partition to SSD, boots but > black screen with cursor -

I've moved the upgraded W10 partition to SSD alongside W7 dual-boot. I used EaseUS Partition Master for the cloning but forgot the boot partition behind on HDD. After much fiddling around with EasyBCD, USB start repairs on both 7 & 10, I recovered the boot partition with EaseUS and copied it to SSD.

Have performed several offline sfc and bootrec cmd lines on both 7 & 10 and the latter boots but doesn't reach the login screen. After the boot screen the screen goes dark and the arrow cursor can move.

There is no Safe Mode, merely the boot screen and options when I run the USB repair. Both sfc and chkdsk are sound and the srt logfile reports: Code: Startup Repair diagnosis and repair log --------------------------- Last successful boot time: ‎11/‎3/‎2016 8:37:57 PM (GMT) Number of repair attempts: 1 Session details System Disk = \Device\Harddisk0 Windows directory = C:\Windows AutoChk Run = 0 Number of root causes = 1 Test Performed: Name: Check for updates Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: Name: System disk test Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: Name: Disk failure diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 0 msTest Performed: --------------------------- Name: Disk metadata test Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Target OS test Result: Completed successfully. Error code = 0x0 Time taken = 16 msTest Performed: --------------------------- Name: Volume content check Result: Completed successfully. Error code = 0x0Time taken = 62 ms Test Performed: --------------------------- Name: Boot manager diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: System boot log diagnosis Result: Completed successfully. Error code = 0x0Time taken = 0 ms Test Performed: --------------------------- Name: Event log diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 47 ms Test Performed: --------------------------- Name: Internal state check Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Boot status test Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Setup state check Result: Completed successfully. Error code = 0x0 Time taken = 156 ms Test Performed: --------------------------- Name: Registry hives test Result: Completed successfully. Error code = 0x0 Time taken = 1563 ms Test Performed: --------------------------- Name: Windows boot log diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Bugcheck analysis Result: Completed successfully. Error code = 0x0 Time taken = 265 ms Test Performed: --------------------------- Name: Access control test Result: Completed successfully. Error code = 0x0 Time taken = 9000 ms Test Performed: --------------------------- Name: File system test (chkdsk) Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Software installation log diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Fallback diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Root cause found: --------------------------- Unspecified changes to system configuration might have caused the problem. Repair action: Result: Failed. Error code = 0x32 Time taken = 172 ms Repair action: System files integrity check and repair Result: Failed. Error code = 0xa1Time taken = 56812 ms ------------------------------------------------------[/quote] As a rule, I don't keep on repeating the same "repair" over & over again hoping for a different result, but I've reached the stage now where I cannot find anything new to try. Can anyone please help?

:)

 

Windows 10 takes too long to shutdown/restart/hibernate

Summary: I have a HD/SSD dual boot (W10/W8.1) machine that I moved the W10 partition from the HD to a partition on the SSD . Shortly after that, the shutdown time increased to about 2 minutes. The problem cleared up when I deleted the boot partitions that
I left on the HD, even though they were hidden and not involved (I thought) in the boot process.

Details:

The machine was originally furnished with a large HD with a Windows partition, a restore partition, and a SYSTEM partition on it. I later added a very large DATA partition for media files. Overtime, I added an SSD (as a dual boot) with W8.1 Pro on it
and later upgraded the OS on the HD to W10 Pro. Everything worked well in this configuration.

Recently, I added the W10 partition to the SSD and inactivated the W10 partition on the HD. This left me with a dual boot of both OSes on the SSD. The BIOS was changed so the machine booted from the SSD and I used EasyBCD to setup the dual boot using only
partitions on the SSD.

Shortly after getting everything to work OK, I noticed that the shutdown time went to about 2 minutes. The disk light flickered every so faintly as it was shutting down. Everything that others had recommended to troubleshoot this condition made no difference
in the shutdown.

I finally deleted the SYSTEM partition on the HD and that made the machine shutdown in a very short time, regardless of which OS was active. I didn't think there was any connection remaining to the HD boot capability, but obviously there was. Since then,
I deleted the original W10 partition (which was hidden) on the HD, leaving only an unused Recovery partition on the HD, as well as a large DATA partition. Everything works well now, Startup, Shutdown, and Hibernation.

I

 

my games would not load

I have also a dual-boot system on a SSD.

XP-32 on the active partition and W10-64 on another one. A third partition is dedicated to data and games, almost empty at the moment.

I have an additional drive (HDD) with only data.

However, W7 => W10 upgrading didn't break my dual-boot menu. I can choose between both even if I rarely choose XP now.

 

Did you keep the same partitioning type between the SSD and the HDD; GPT vs. MBR?

 

I had assumed that the ex-W7 partition onto which W10 had been upgraded had been MBR and so that issue never really arose in my queries. I have never been in the position to choose between the two.

 

Go back and clone all the drive again you can mess about trying to work out what's changed but it's quicker to re clone

 

Oops, I deleted it..................I know, I know.

I never even thought of cloning it onto a spare HDD in a caddy.

Now that I think about it in retrospect, there is an entirely better path to the entire procdure that I could have chosen which involves another disk altogether.

 

Could this be the reason behind my inability to login? https://support.microsoft.com/en-us/kb/223188