I did a fresh install to Windows 10 this past week and have seen a few
strange behaviors that I've googled but didn't get any real advice so I
thought I'd ask the what I think are the smarted people on the planet :)
Before I did the upgrade I made a system image of my Win7 Pro and directed
it to my external USB drive. This external drive also maintains my weekly
My Documents backup.
I did the Win 10 install, and then copied my backup of My Documents data
from the external drive into My Documents on my C drive. So far so good.
But out of curiosity, on the external USB drive, I did a right click on the
win7 system image and selected properties just to see how big it was. I was
confused as it said 0KB. So I double clicked on the folder and was
presented with a message stating I didn't have access to that folder (even
though I am the admin and am using the same credentials used with Win 7).
So I right clicked again and selected sharing and was then allowed access
to the system image folder. However when I tried to drill into each folder
in the system image, I ran into the same message and had to share each
folder. Once I did that for all the sub folders I was then able to return
to the root drive and right click on the system image folder and could see
that it was 101gb.
So I'm perplexed as to why I didn't have access to a system image residing
in the same location as my documents, which I did have access to???
And second 'bug', today I installed my backup application (Karen's
Replicator) and then copied all my settings from my backup into the
application setting folder. When I ran the application my settings were not
there so I checked the folder where they are located (which I just copied
them to), and I right clicked on the settings.txt file and was presented
with a dialog that said 'file doesn't exist - would you like to create it'?
So I said yes, and then another dialog said I couldn't create the file
because it already exists???? WTH??? So I rebooted and tried again and the
same thing happened?
I'm scratching my head...
One of my buddies suggested maybe the ram is going bad, but I haven't
noticed anything out of the ordinary other than these two anomalies. So
tomorrow i will pull the ram and rub an eraser over it and re-seat them and
try again.
Comments anyone?
Anyone else having flaky stuff happen with Win 10?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.