carmen617
Well-Known Member
- Reaction score
- 753
- Location
- Boston, MA
I'd be interested in knowing why it works as well. Sequence of events as follows: system is a refurb purchased from MicroCenter with a refurb license of Windows 7 Pro on it, no bloatware. I started from opening the box, so did the original boot of Windows 7, chose timezone and gave it a user name, then immediately did a Windows 10 upgrade from a USB. I don't do the online updates as I find that takes forever, so after the upgrade, I checked for and installed Windows updates. After that I hooked up the old system's boot drive to the new system with a USB dock, and copied over the contents of the user files including appdata. Then I hooked up the 2TB data drive, saw it was pretty full, realized my client's instructions (move the data from the 2TB drive over, I want the drive back) could only be fulfilled by installing the drive into the system, physically installed it, and then my problems started.
I want to thank everybody here for your help and suggestions. Since the Windows Memory Diagnostics worked I've searched for it specifically online and found references to it, but no source of the original reason to try it, or why it works. Will certainly put this into my memory banks, but would love to know why the problem and why the solution works!
I want to thank everybody here for your help and suggestions. Since the Windows Memory Diagnostics worked I've searched for it specifically online and found references to it, but no source of the original reason to try it, or why it works. Will certainly put this into my memory banks, but would love to know why the problem and why the solution works!
Last edited: