New
#31
This makes me think Mac OS X on a Windows PC. VMware on OSx86......PC booted to "X:/v::", Windows XP Pro on a hidden, virtual HDD
See why: Vmware - OSx86
I can be of no help here!
This makes me think Mac OS X on a Windows PC. VMware on OSx86......PC booted to "X:/v::", Windows XP Pro on a hidden, virtual HDD
See why: Vmware - OSx86
I can be of no help here!
You were probably checking the Security tab of the Properties dialog box for the root of the OS drive. Take a look at the OP's screenshot again:
While the "C" drive is highlighted in the left navigation pane, the All Users folder is highlighted in the right pane. The Properties dialog box shown in the foreground is for the folder named All Users. You can see All Users Properties as the title of that dialog box.
Your reply to Layback Bear asking, "Are you able to run sfc /scannow?" was: "I did - it said no problems."
Then you went on to totally confuse me with:
Could you please restate that info another way?
Were you running the SFC scan from WinRE (like this)?
I'm not convinced that there is a VM - naughty or otherwise - when you boot to your W7 OS.
There is not much that I can say about the virus redirecting you (mentioned at the end of post #6). Do you still have the shortcut? If yes, can you please post a screenshot of the Properties > Shortcut tab?
Which settings won't hold? You will need to be more specific than that.
The first tab seems to indicate that you searched Yahoo for twc email. The second tab is presented to you from a Yahoo server. There is no evidence that this is the result of a hijack, infection or redirect. However, I have no idea what you clicked on in Yahoo's search returns to get to there.
There is nothing wrong with being denied access to the Documents and Setting folder. That is supposed to be that way. There is nothing wrong with the date/time stamp on the folder named PerLogs. The date/time stamp on the folder named Recovery might have been changed by one of the tools that you booted to for offline scans.
There are a few reasons why the autoexec.bat file might have been created. It is not hurting anything.