F5F Stay Refreshed Software Operating Systems Windows 10 isn't working properly with the second HDD from Windows 7.

Windows 10 isn't working properly with the second HDD from Windows 7.

Windows 10 isn't working properly with the second HDD from Windows 7.

Pages (2): 1 2 Next
F
fashianicolle
Member
66
06-11-2016, 09:51 PM
#1
I performed a new installation of Windows 10 and am using the same 2TB HDD from when I had Windows 7. I've adjusted permissions on the drive and folders, but everything is still broken. It mentions needing permission from DESKTOP\steve, even though I'm logged in as that user. I can't copy or delete files, etc., which is really annoying. I've logged out and back in, rebooted, but it doesn’t work. I’m planning to switch back to Windows 7 since this never happened before. Any advice?
F
fashianicolle
06-11-2016, 09:51 PM #1

I performed a new installation of Windows 10 and am using the same 2TB HDD from when I had Windows 7. I've adjusted permissions on the drive and folders, but everything is still broken. It mentions needing permission from DESKTOP\steve, even though I'm logged in as that user. I can't copy or delete files, etc., which is really annoying. I've logged out and back in, rebooted, but it doesn’t work. I’m planning to switch back to Windows 7 since this never happened before. Any advice?

Z
zamys
Senior Member
690
06-12-2016, 05:47 AM
#2
No need to unmount, just format the data as required. Do you have the information you need?
Z
zamys
06-12-2016, 05:47 AM #2

No need to unmount, just format the data as required. Do you have the information you need?

R
RageGlitch
Posting Freak
771
06-12-2016, 07:43 AM
#3
You can safely unmount it since it's 95% full.
R
RageGlitch
06-12-2016, 07:43 AM #3

You can safely unmount it since it's 95% full.

T
TaZog
Junior Member
35
06-15-2016, 01:51 AM
#4
The issue likely stems from your new installation sharing the same username or device name as your previous account. Your old Windows 7 machine was named "DESKTOP" with the user "Steve," identical to your current setup. The confusion arises because Windows displays "DESKTOP\Steve" and you mistakenly believe it's your active session, when it actually belongs to the previous install. Verify this by checking the GUID associated with the account. To restore access, run an admin command prompt and execute the specified commands. Be prepared for a warning about ACL changes—disregard it as it’s necessary. The second command will reset permissions for Administrators, and you’ll notice the recycle bin on that drive appears corrupt after accessing D:; this is normal and can be ignored since the system will rebuild it. Let me know if this resolves your concerns. For a large data volume, the process may take some time. Edited December 9, 2017 by Tabs Fixed third command
T
TaZog
06-15-2016, 01:51 AM #4

The issue likely stems from your new installation sharing the same username or device name as your previous account. Your old Windows 7 machine was named "DESKTOP" with the user "Steve," identical to your current setup. The confusion arises because Windows displays "DESKTOP\Steve" and you mistakenly believe it's your active session, when it actually belongs to the previous install. Verify this by checking the GUID associated with the account. To restore access, run an admin command prompt and execute the specified commands. Be prepared for a warning about ACL changes—disregard it as it’s necessary. The second command will reset permissions for Administrators, and you’ll notice the recycle bin on that drive appears corrupt after accessing D:; this is normal and can be ignored since the system will rebuild it. Let me know if this resolves your concerns. For a large data volume, the process may take some time. Edited December 9, 2017 by Tabs Fixed third command

S
searaydude
Member
67
06-15-2016, 02:32 AM
#5
Add your Win10 Steve admin with complete privileges and verify inherited child settings. Review the permissions listed in the Audit and Access sections, noting that the Steve account appears as a Win7 profile on the drive. This issue occurs because the system treats it as a different operating environment.
S
searaydude
06-15-2016, 02:32 AM #5

Add your Win10 Steve admin with complete privileges and verify inherited child settings. Review the permissions listed in the Audit and Access sections, noting that the Steve account appears as a Win7 profile on the drive. This issue occurs because the system treats it as a different operating environment.

F
FlamingTiger9
Member
235
06-17-2016, 10:48 PM
#6
Your Win7 account was named "Home," not "Steve." You set up another admin account called "admin," but it's experiencing the same problems.
F
FlamingTiger9
06-17-2016, 10:48 PM #6

Your Win7 account was named "Home," not "Steve." You set up another admin account called "admin," but it's experiencing the same problems.

A
ACORNMAN
Junior Member
47
06-19-2016, 07:47 AM
#7
The documentation outlined my approach using GUI, yet I opted for command-line methods instead.
A
ACORNMAN
06-19-2016, 07:47 AM #7

The documentation outlined my approach using GUI, yet I opted for command-line methods instead.

S
squirelymayo
Member
89
06-19-2016, 01:30 PM
#9
I checked your steps and didn't mention removing a password. Just plugging in the SSD with Windows 7 is fine, but make sure you back up any important data first.
S
squirelymayo
06-19-2016, 01:30 PM #9

I checked your steps and didn't mention removing a password. Just plugging in the SSD with Windows 7 is fine, but make sure you back up any important data first.

S
161
06-19-2016, 08:45 PM
#10
The full 10-step method matches exactly what your recent post outlines. @Mr. Chicken Sandwich seems to be familiar with command prompts, which makes the longer explanation confusing. Edit: Also, password protection isn't related here—Windows ACLs don't work that way. It only impacts files with EFS enabled.
S
Smart_man_0709
06-19-2016, 08:45 PM #10

The full 10-step method matches exactly what your recent post outlines. @Mr. Chicken Sandwich seems to be familiar with command prompts, which makes the longer explanation confusing. Edit: Also, password protection isn't related here—Windows ACLs don't work that way. It only impacts files with EFS enabled.

Pages (2): 1 2 Next