Further Win10 upgrade adventures.

I have one computer with two HDDs:

1/ STD with Win7 Ult installed
2/ PRV with Win10 pro installed over Win8 in Aug15.

PRV works well, and I use this for Internet downloads, mainly
overnight on off-peak rates. I then move various relevant files over
to STD when required, and leave the rest on PRV.

I have just done an upgrade to Win10 pro on STD over Win7 ult that has
gone well though this took a long time. Outlook10 disappeared but I
found it via a search for its shortcut.

Then I booted over to PRV and found some files to transfer to STD, and
as usual I used the 'move' to transfer these to the folder 'Pictures'
on STD. I was refused access to this folder and asked if I wanted
permanent access to it. I selected 'yes' and this started the HDDs
thrashing for a while and the files disappeared from PRV.

Booting back to STD I found the new Win10 pro upgrade corrupted with
many applications not working, the transferred files form above not
present, the start menu not working, the Office10 applications all
missing their 'links' or missing various files. Error messages such
as they were included ''permissions'' in their texts.

I assumed the Win10 upgrade would at least have loaded a System
Restore point at its end, but no, it had not. A glaring omission!

So I had to restore back to Win7 ult via a Macrium image, and repeat
the whole tedious upgrade again, and I'm at this point now. And I had
to load a System Restore point manually! And do daily image backups
too.

Can anyone advise why this corruption occurs? This happened before in
August. How am I to transfer files from PRV to STD & visa versa
safely?
Peter

Peter Jason wrote:
I have one computer with two HDDs:

1/ STD with Win7 Ult installed
2/ PRV with Win10 pro installed over Win8 in Aug15.

PRV works well, and I use this for Internet downloads, mainly
overnight on off-peak rates. I then move various relevant files over
to STD when required, and leave the rest on PRV.

I have just done an upgrade to Win10 pro on STD over Win7 ult that has
gone well though this took a long time. Outlook10 disappeared but I
found it via a search for its shortcut.

Then I booted over to PRV and found some files to transfer to STD, and
as usual I used the 'move' to transfer these to the folder 'Pictures'
on STD. I was refused access to this folder and asked if I wanted
permanent access to it. I selected 'yes' and this started the HDDs
thrashing for a while and the files disappeared from PRV.

Booting back to STD I found the new Win10 pro upgrade corrupted with
many applications not working, the transferred files form above not
present, the start menu not working, the Office10 applications all
missing their 'links' or missing various files. Error messages such
as they were included ''permissions'' in their texts.

I assumed the Win10 upgrade would at least have loaded a System
Restore point at its end, but no, it had not. A glaring omission!

So I had to restore back to Win7 ult via a Macrium image, and repeat
the whole tedious upgrade again, and I'm at this point now. And I had
to load a System Restore point manually! And do daily image backups
too.

Can anyone advise why this corruption occurs? This happened before in
August. How am I to transfer files from PRV to STD & visa versa
safely?
Peter

Are you using TrueCrypt or BitLocker ?

It almost seems as if your login ID doesn't
match the files in that profile. Normally,
you would expect the account created, to match
the permissions in the section of file tree
associated with that account.

Did you apply an MSA to an existing local account ?

Have you been redirecting Pictures and Video to
your D: drive, instead of accepting the default
setup of storing your account stuff on the
current C: drive ?

There have to be some differences between how
you're doing things, and how everyone else is
doing things.

I *do* run into the problem of not having
permissions to place files somewhere. And the
OS will propagate changes of ownership, down
the tree when I attempt to access a higher level
folder.

*******

In an elevated Command Prompt window

wmic useraccount get name,sid

this gives me the accounts on my installed C: .

Name SID
Administrator S-1-5-21-3768549767-1934788099-1503758287-500
Mere User S-1-5-21-3768549767-1934788099-1503758287-1000
Guest S-1-5-21-3768549767-1934788099-1503758287-501

Using the Advanced tab on file properties, or using icacls
(as in this example), I can get some security info. Even
as administrator, there should be as many errors in the
CErr.txt file, as there are junction points in the partition.

icacls c:\ /save "%userprofile%\Downloads\ntfsCdrive.txt" /t /c "%userprofile%\Downloads\CErr.txt" 2&1

D:AI(A;OICIID;FA;;;SY) --- SYSTEM ???
(A;OICIID;FA;;;BA) --- Built-in Administrator ???
(A;OICIID;FA;;;S-1-5-21-3768549767-1934788099-1503758287-1000) --- my local account
(A;OICIID;FA;;;S-1-5-21-2394456921-3258211444-2531705128-1001) --- an account from
another OS run

In that example, I may have applied the equivalent of "TakeOwn"
to a file, and now as far as I know, I can manipulate that
from two OSes. I haven't tested how many
of those I can apply.

But that kind of thing cannot account for your symptoms.
It's almost as if your account credentials aren't the
same as before.

*******

An OS upgrade creates Windows.old, to hold the old OS.
And there is a separate place in WIn10 to select "revert"
to go back to the old OS. System Restore is not turned on,
on purpose. The entire Windows partition is kept instead.
The Windows.old will be deleted automatically after
30 days, or it can be removed with Disk Cleanup. But
this does not cover changes to C:\Program Files,
and this is why a backup is a more appropriate kind
of protection, than anything Windows is providing.

That's the one good part of your story - you had a backup.

Paul

On Mon, 28 Dec 2015 19:39:44 -0500, Paul wrote:

Peter Jason wrote:
I have one computer with two HDDs:

1/ STD with Win7 Ult installed
2/ PRV with Win10 pro installed over Win8 in Aug15.

PRV works well, and I use this for Internet downloads, mainly
overnight on off-peak rates. I then move various relevant files over
to STD when required, and leave the rest on PRV.

I have just done an upgrade to Win10 pro on STD over Win7 ult that has
gone well though this took a long time. Outlook10 disappeared but I
found it via a search for its shortcut.

Then I booted over to PRV and found some files to transfer to STD, and
as usual I used the 'move' to transfer these to the folder 'Pictures'
on STD. I was refused access to this folder and asked if I wanted
permanent access to it. I selected 'yes' and this started the HDDs
thrashing for a while and the files disappeared from PRV.

Booting back to STD I found the new Win10 pro upgrade corrupted with
many applications not working, the transferred files form above not
present, the start menu not working, the Office10 applications all
missing their 'links' or missing various files. Error messages such
as they were included ''permissions'' in their texts.

I assumed the Win10 upgrade would at least have loaded a System
Restore point at its end, but no, it had not. A glaring omission!

So I had to restore back to Win7 ult via a Macrium image, and repeat
the whole tedious upgrade again, and I'm at this point now. And I had
to load a System Restore point manually! And do daily image backups
too.

Can anyone advise why this corruption occurs? This happened before in
August. How am I to transfer files from PRV to STD & visa versa
safely?
Peter

Are you using TrueCrypt or BitLocker ?

Bit Locker yes, truecrypt no. But this has always been so.

It almost seems as if your login ID doesn't
match the files in that profile. Normally,
you would expect the account created, to match
the permissions in the section of file tree
associated with that account.

Did you apply an MSA to an existing local account ?

No. I have no idea what MSA is.

Have you been redirecting Pictures and Video to
your D: drive, instead of accepting the default
setup of storing your account stuff on the
current C: drive ?

I have been sorting images & downloads; some on the PRV drive and some
on the C: drive.
Should I use another drive (a USB drive?) as an intermediate?

There have to be some differences between how
you're doing things, and how everyone else is
doing things.

I *do* run into the problem of not having
permissions to place files somewhere. And the
OS will propagate changes of ownership, down
the tree when I attempt to access a higher level
folder.

*******

In an elevated Command Prompt window

wmic useraccount get name,sid

this gives me the accounts on my installed C: .

Name SID
Administrator S-1-5-21-3768549767-1934788099-1503758287-500
Mere User S-1-5-21-3768549767-1934788099-1503758287-1000
Guest S-1-5-21-3768549767-1934788099-1503758287-501

Using the Advanced tab on file properties, or using icacls
(as in this example), I can get some security info. Even
as administrator, there should be as many errors in the
CErr.txt file, as there are junction points in the partition.

icacls c:\ /save "%userprofile%\Downloads\ntfsCdrive.txt" /t /c "%userprofile%\Downloads\CErr.txt" 2&1

D:AI(A;OICIID;FA;;;SY) --- SYSTEM ???
(A;OICIID;FA;;;BA) --- Built-in Administrator ???
(A;OICIID;FA;;;S-1-5-21-3768549767-1934788099-1503758287-1000) --- my local account
(A;OICIID;FA;;;S-1-5-21-2394456921-3258211444-2531705128-1001) --- an account from
another OS run

In that example, I may have applied the equivalent of "TakeOwn"
to a file, and now as far as I know, I can manipulate that
from two OSes. I haven't tested how many
of those I can apply.

But that kind of thing cannot account for your symptoms.
It's almost as if your account credentials aren't the
same as before.

*******

An OS upgrade creates Windows.old, to hold the old OS.
And there is a separate place in WIn10 to select "revert"
to go back to the old OS. System Restore is not turned on,
on purpose. The entire Windows partition is kept instead.
The Windows.old will be deleted automatically after
30 days, or it can be removed with Disk Cleanup. But
this does not cover changes to C:\Program Files,
and this is why a backup is a more appropriate kind
of protection, than anything Windows is providing.

That's the one good part of your story - you had a backup.

Paul