Need immediate help

Joined
Sep 16, 2016
Messages
3
Reaction score
0
So I was installing Windows 10 on a spare HDD while in my computer, and I had it plugged in along with my computer's HDD. After install, I copied some files from the original and I had to go through UAC to get it multiple times. Finished setting up the spare one, and plugged it out. So I booted back to my original one and it just seemed to have problems now.

The computer seems to be slow. Like if I open up a folder, it'd just take a couple of seconds to open.
The start menu is unresponsive. Apps on the task bar lost their icons, were just blank white icons, or normal. However, if I opened up any of them, I'd get an error saying something along the lines of "Can't read *insert stuff I don't remember" or "Can't write, etc etc etc". Now I think this has something to do with permissions and the like.
So if I open up an application, I figured I needed to run as admin because some wouldn't work without it.
Task manager boots up so slooooow.
Overall my OS seems very buggy.

I need help immediately.
I can provide more information about this problem.
Thanks.
 
Joined
Oct 1, 2014
Messages
2,334
Reaction score
358
I suppose you were online when you installed the second copy of Win 10? You might check the activation page in Settings to see if you still show a digital entitlement or current activation.

I only guess might be by installing another copy with the original one still available something on the system is being confused and looking for things that are not currently on that system since you removed that second drive.

The boot files should still be where they were depending on what type of system you have so you might do a couple of things.

First would be to get a Disk Management picture of your system. Use the snipping tool to take the picture showing the graphical descriptions of the partitions and attach.

Secondly, open an Administrative command prompt and type

bcdedit /enum all > %userprofile%\Desktop\bcdlist.txt

and attach that text file from your desktop.
 
Joined
Sep 16, 2016
Messages
3
Reaction score
0
My Windows activation seems fine.
My opinion would be that windows is confusing the admin stuff, because apps seem to be unable to access files like Word's autocorrect files without running as admin, and browser profiles, and I believe this is due to granting access to the other OS while I was copying files.



pSFXnJx.png



Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=G:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {457b82fb-6bb4-11e6-a30a-c53a9d26ef93}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {cd667b2d-6bb4-11e6-a30a-c53a9d26ef93}
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {457b82fb-6bb4-11e6-a30a-c53a9d26ef93}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {93f0e0d3-3be2-11e6-9e86-943c16535f89}
device ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{93f0e0d4-3be2-11e6-9e86-943c16535f89}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
displaymessageoverride Recovery
osdevice ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{93f0e0d4-3be2-11e6-9e86-943c16535f89}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Windows Boot Loader
-------------------
identifier {cd667b2d-6bb4-11e6-a30a-c53a9d26ef93}
device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{cd667b2e-6bb4-11e6-a30a-c53a9d26ef93}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{cd667b2e-6bb4-11e6-a30a-c53a9d26ef93}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Resume from Hibernate
---------------------
identifier {457b82fb-6bb4-11e6-a30a-c53a9d26ef93}
device partition=C:
path \WINDOWS\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {cd667b2d-6bb4-11e6-a30a-c53a9d26ef93}
recoveryenabled Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {93f0e0d1-3be2-11e6-9e86-943c16535f89}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {93f0e0d3-3be2-11e6-9e86-943c16535f89}
recoveryenabled Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=G:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {93f0e0d4-3be2-11e6-9e86-943c16535f89}
description Windows Recovery
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {93f0e0d5-3be2-11e6-9e86-943c16535f89}
description Windows Setup
ramdisksdidevice partition=C:
ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

Device options
--------------
identifier {cd667b2e-6bb4-11e6-a30a-c53a9d26ef93}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume5
ramdisksdipath \Recovery\WindowsRE\boot.sdi
 
Joined
Oct 1, 2014
Messages
2,334
Reaction score
358
I suppose what I see if you are booting from the G: partition to the OS on Disk 1 or C. I see not Boot Loader for the OS on Disk 0. Is that what you are expecting? Will the system boot if you remove Disk 1?

Both G: and C: are active partitions so you may be able to set disk 1 as the primary boot drive and boot from it, depending on how you did the install.

What exactly did you do to give access during the file copy process.

I don't know how running the same licensed version of an OS at the same time will effect your system.
 
Joined
Sep 16, 2016
Messages
3
Reaction score
0
I'm booting from partition C:, Disk 1, I believe. Unfortunately I'd just found out I can't boot to the Drive (1) with the OS without my secondary drive (0) (not the one I installed another OS with).

When I was accessing the Disk (OS), Users, there was a prompt in which I had to click it to gain permanent access, I think it was UAC.

Tried to fix it myself, but I really can't. I can't resort to reinstalling Windows and reinstalling my stuff all over again. I've tried "refreshing" it, but it didn't work. Reset, however, I didn't try.
 
Joined
Oct 1, 2014
Messages
2,334
Reaction score
358
I'm booting from partition C:, Disk 1, I believe.
To make things a little more clear, the boot files are in the second partition on Disk 0, designated as "System". The Disk numbers come directly from the Disk Management picture so the First disk is 0 and the second is 1.

These boot files send you to the first partition on Disk 1 for the OS, designated as "Boot"... So, if Disk 1 is the second install that is what you are running in. And I see no option to boot into an OS on the second partition of the first disk (disk 0).

When you start explaining drive numbers and letters and disks, it can become confusing. So which partition contains your original Win 10 install..
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top