S
SysopChris
First, if I am not referencing this original post correctly I apologize and will be glad to correct my mistake if shown how.
Thank you for your time.
This was the original question.
Accessing old drive from new drive OS - security problems, corruption?
I recently got a new SSD to compliment my old HDD. I decided to do a fresh install of Windows 10 on the SSD while leaving the old HDD operating (upgraded Win10) system intact, with the idea that I could boot into the old OS to use any programs that I couldn't easily reinstall or that I didn't want to take up space on the new drive because I rarely use them. I would also use the HDD to store all of the data, e.g. pictures, documents, etc. (at this point all of my data is still on it anyway)....
The answer was below.
A. User
2. Does the check box for "Replace all child object auditing entries..." ever get checked?
I have using some of these drives for 6 years and gone through many variation of this process for up to 8 drives after every clean install. I want to fine the settings that will prevent this from happening again. I am part of a private network.
Sometimes my process corrupts the recycle bin for a particular drive.
Thanks,
Chris Lively
Here is some system info. Once again if there's a standard method of adding this to a post please let me know.
System Information report written at: 06/23/20 23:14:33
System Name: TANELORN
[Drives]
Item Value
Drive C:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 110.80 GB (118,971,621,376 bytes)
Free Space 47.42 GB (50,916,667,392 bytes)
Volume Name
Volume Serial Number E469526A
Drive D:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 232.28 GB (249,413,234,688 bytes)
Free Space 151.97 GB (163,176,456,192 bytes)
Volume Name Atlas
Volume Serial Number 6C9BADE3
Drive E:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 4.55 TB (5,000,970,235,904 bytes)
Free Space 132.36 GB (142,124,326,912 bytes)
Volume Name Enlil
Volume Serial Number F251955B
Drive F:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 3.64 TB (4,000,778,633,216 bytes)
Free Space 388.75 GB (417,415,708,672 bytes)
Volume Name Hades
Volume Serial Number 6260AFB0
Drive G:
Description Local Fixed Disk
Compressed No
File System exFAT
Size 7.28 TB (8,001,528,266,752 bytes)
Free Space 762.38 GB (818,599,165,952 bytes)
Volume Name Thoth
Volume Serial Number D48E52CD
Drive H:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 298.09 GB (320,071,528,448 bytes)
Free Space 5.51 GB (5,915,136,000 bytes)
Volume Name Enclosure
Volume Serial Number 24ECCA7B
Drive I:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 3.64 TB (4,000,774,615,040 bytes)
Free Space 1.60 TB (1,764,283,293,696 bytes)
Volume Name Apollo
Volume Serial Number 547F79D0
Drive J:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 3.64 TB (4,000,751,546,368 bytes)
Free Space 234.87 GB (252,186,755,072 bytes)
Volume Name Enki
Volume Serial Number CA0ABC13
Drive L:
Description CD-ROM Disc
<?xml version="1.0"?>
<MsInfo>
<Metadata>
<Version>8.0</Version>
<CreationUTC>06/24/20 03:09:15</CreationUTC>
</Metadata>
<Category name="System Summary">
<Data>
<Item><![CDATA[OS Name]]></Item>
<Value><![CDATA[Microsoft Windows 10 Pro]]></Value>
</Data>
<Data>
<Item><![CDATA[Version]]></Item>
<Value><![CDATA[10.0.18363 Build 18363]]></Value>
</Data>
<Data>
<Item><![CDATA[Other OS Description ]]></Item>
<Value><![CDATA[Not Available]]></Value>
</Data>
<Data>
<Item><![CDATA[OS Manufacturer]]></Item>
<Value><![CDATA[Microsoft Corporation]]></Value>
</Data>
<Data>
<Item><![CDATA[System Name]]></Item>
<Value><![CDATA[TANELORN]]></Value>
</Data>
<Data>
<Item><![CDATA[System Manufacturer]]></Item>
<Value><![CDATA[System manufacturer]]></Value>
</Data>
<Data>
<Item><![CDATA[System Model]]></Item>
<Value><![CDATA[System Product Name]]></Value>
</Data>
<Data>
<Item><![CDATA[System Type]]></Item>
<Value><![CDATA[x64-based PC]]></Value>
</Data>
<Data>
<Item><![CDATA[System SKU]]></Item>
<Value><![CDATA[SKU]]></Value>
</Data>
<Data>
<Item><![CDATA[Processor]]></Item>
<Value><![CDATA[Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3504 Mhz, 4 Core(s), 4 Logical Processor(s)]]></Value>
</Data>
<Data>
<Item><![CDATA[BIOS Version/Date]]></Item>
<Value><![CDATA[American Megatrends Inc. 3301, 1/13/2017]]></Value>
</Data>
<Data>
<Item><![CDATA[SMBIOS Version]]></Item>
<Value><![CDATA[3.0]]></Value>
</Data>
<Data>
<Item><![CDATA[Embedded Controller Version]]></Item>
<Value><![CDATA[255.255]]></Value>
</Data>
<Data>
<Item><![CDATA[BIOS Mode]]></Item>
<Value><![CDATA[UEFI]]></Value>
</Data>
<Data>
<Item><![CDATA[BaseBoard Manufacturer]]></Item>
<Value><![CDATA[ASUSTeK COMPUTER INC.]]></Value>
</Data>
<Data>
<Item><![CDATA[BaseBoard Product]]></Item>
<Value><![CDATA[Z170-A]]></Value>
</Data>
<Data>
<Item><![CDATA[BaseBoard Version]]></Item>
<Value><![CDATA[Rev 1.xx]]></Value>
Continue reading...
Thank you for your time.
This was the original question.
Accessing old drive from new drive OS - security problems, corruption?
I recently got a new SSD to compliment my old HDD. I decided to do a fresh install of Windows 10 on the SSD while leaving the old HDD operating (upgraded Win10) system intact, with the idea that I could boot into the old OS to use any programs that I couldn't easily reinstall or that I didn't want to take up space on the new drive because I rarely use them. I would also use the HDD to store all of the data, e.g. pictures, documents, etc. (at this point all of my data is still on it anyway)....
The answer was below.
A. User
- Microsoft Agent
|
- Moderator
Hi Keith,
The error message that you're getting likely occurs if you don't have a permission to access system files or if there's a conflict between multiple files on your system. These access permissions restrict unauthorized users and external resources from accessing system files and folders. To troubleshoot your issue with opening documents, we suggest setting the permission of your hard drive to full control. To do so. here's how:
My follow up question is concerning this image which appears to from a newly installed system.
https://filestore.community.support.microsoft.com/api/images/0217871d-d4e7-440d-81c5-4237c6a1e1c4
The instructions are perfect and I totally agree, it worked for me.
My question is, unlike the example above, I have other Principals and Group or User names here.
https://filestore.community.support.microsoft.com/api/images/17f2d1fe-955c-4516-96f8-ab1eeccd16fb
These are from other Windows installs I have had these external USB hard drives connected to. Same had the same system name, others did not. Some are long names like 's-...'.
1. Is it a best practice to delete the other Principals and Group or User names after I add 'Everyone' from these three places:
a) Permissions for drive.
b) Advanced Security Settings Permissions.
c) Advanced Security Settings Auditing.
2. Does the check box for "Replace all child object auditing entries..." ever get checked?
I have using some of these drives for 6 years and gone through many variation of this process for up to 8 drives after every clean install. I want to fine the settings that will prevent this from happening again. I am part of a private network.
Sometimes my process corrupts the recycle bin for a particular drive.
Thanks,
Chris Lively
Here is some system info. Once again if there's a standard method of adding this to a post please let me know.
System Information report written at: 06/23/20 23:14:33
System Name: TANELORN
[Drives]
Item Value
Drive C:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 110.80 GB (118,971,621,376 bytes)
Free Space 47.42 GB (50,916,667,392 bytes)
Volume Name
Volume Serial Number E469526A
Drive D:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 232.28 GB (249,413,234,688 bytes)
Free Space 151.97 GB (163,176,456,192 bytes)
Volume Name Atlas
Volume Serial Number 6C9BADE3
Drive E:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 4.55 TB (5,000,970,235,904 bytes)
Free Space 132.36 GB (142,124,326,912 bytes)
Volume Name Enlil
Volume Serial Number F251955B
Drive F:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 3.64 TB (4,000,778,633,216 bytes)
Free Space 388.75 GB (417,415,708,672 bytes)
Volume Name Hades
Volume Serial Number 6260AFB0
Drive G:
Description Local Fixed Disk
Compressed No
File System exFAT
Size 7.28 TB (8,001,528,266,752 bytes)
Free Space 762.38 GB (818,599,165,952 bytes)
Volume Name Thoth
Volume Serial Number D48E52CD
Drive H:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 298.09 GB (320,071,528,448 bytes)
Free Space 5.51 GB (5,915,136,000 bytes)
Volume Name Enclosure
Volume Serial Number 24ECCA7B
Drive I:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 3.64 TB (4,000,774,615,040 bytes)
Free Space 1.60 TB (1,764,283,293,696 bytes)
Volume Name Apollo
Volume Serial Number 547F79D0
Drive J:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 3.64 TB (4,000,751,546,368 bytes)
Free Space 234.87 GB (252,186,755,072 bytes)
Volume Name Enki
Volume Serial Number CA0ABC13
Drive L:
Description CD-ROM Disc
<?xml version="1.0"?>
<MsInfo>
<Metadata>
<Version>8.0</Version>
<CreationUTC>06/24/20 03:09:15</CreationUTC>
</Metadata>
<Category name="System Summary">
<Data>
<Item><![CDATA[OS Name]]></Item>
<Value><![CDATA[Microsoft Windows 10 Pro]]></Value>
</Data>
<Data>
<Item><![CDATA[Version]]></Item>
<Value><![CDATA[10.0.18363 Build 18363]]></Value>
</Data>
<Data>
<Item><![CDATA[Other OS Description ]]></Item>
<Value><![CDATA[Not Available]]></Value>
</Data>
<Data>
<Item><![CDATA[OS Manufacturer]]></Item>
<Value><![CDATA[Microsoft Corporation]]></Value>
</Data>
<Data>
<Item><![CDATA[System Name]]></Item>
<Value><![CDATA[TANELORN]]></Value>
</Data>
<Data>
<Item><![CDATA[System Manufacturer]]></Item>
<Value><![CDATA[System manufacturer]]></Value>
</Data>
<Data>
<Item><![CDATA[System Model]]></Item>
<Value><![CDATA[System Product Name]]></Value>
</Data>
<Data>
<Item><![CDATA[System Type]]></Item>
<Value><![CDATA[x64-based PC]]></Value>
</Data>
<Data>
<Item><![CDATA[System SKU]]></Item>
<Value><![CDATA[SKU]]></Value>
</Data>
<Data>
<Item><![CDATA[Processor]]></Item>
<Value><![CDATA[Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3504 Mhz, 4 Core(s), 4 Logical Processor(s)]]></Value>
</Data>
<Data>
<Item><![CDATA[BIOS Version/Date]]></Item>
<Value><![CDATA[American Megatrends Inc. 3301, 1/13/2017]]></Value>
</Data>
<Data>
<Item><![CDATA[SMBIOS Version]]></Item>
<Value><![CDATA[3.0]]></Value>
</Data>
<Data>
<Item><![CDATA[Embedded Controller Version]]></Item>
<Value><![CDATA[255.255]]></Value>
</Data>
<Data>
<Item><![CDATA[BIOS Mode]]></Item>
<Value><![CDATA[UEFI]]></Value>
</Data>
<Data>
<Item><![CDATA[BaseBoard Manufacturer]]></Item>
<Value><![CDATA[ASUSTeK COMPUTER INC.]]></Value>
</Data>
<Data>
<Item><![CDATA[BaseBoard Product]]></Item>
<Value><![CDATA[Z170-A]]></Value>
</Data>
<Data>
<Item><![CDATA[BaseBoard Version]]></Item>
<Value><![CDATA[Rev 1.xx]]></Value>
Continue reading...