Solved Problems saving .doc and .txt files to my desktop

[pheonix73]

On my Windows 7 Home Premium (x64) I recently started receiving an error when trying to save a document (.doc, .xls, etc) or text (.txt)file to my desktop. The error is as follows:

"C:\Users\John\Desktop\(FILE NAME).doc
You don't have permission to save in this location.
Contact the administrator to obtain permission.

Would you like to save in the My Documents folder instead?"

I am the only user profile on this computer and it is set as administrator. I currently have all security permissions set to "Allow All" and I have no password set, so what is going on and how do I fix it? If I select "Yes" to save it to My Document, then move the file to my desktop, I am only able to open the file in a non-editable mode/version.

 

[andrew129260]

Something is def odd there. Certainly not normal.

Try to take ownership of your profile folder under C\users

http://www.sevenforums.com/tutorials/1911-take-ownership-shortcut.html

http://www.sevenforums.com/tutorials/129063-take-ownership-allow-prevent-users-groups.html

 

[pheonix73]

Something is def odd there. Certainly not normal.

Try to take ownership of your profile folder under C\users

http://www.sevenforums.com/tutorials/1911-take-ownership-shortcut.html

http://www.sevenforums.com/tutorials/129063-take-ownership-allow-prevent-users-groups.html

"Take ownership" doesn't show up in any of my context menus. I do have full permissions set in the properties>security menu, though. (First link you provided)

"C:\Windows\System32\secpol.msc" can not be found by my Windows system. (Second link you provided)

 

[Ztruker]

Read the directions at the Take Ownership Shortcut andrew posted. That shows you how to add Take Ownership to your right click Context menu.

 

[pheonix73]

Read the directions at the Take Ownership Shortcut andrew posted. That shows you how to add Take Ownership to your right click Context menu.

I downloaded, and installed, Add_Take_Ownership.reg, but as I said before, "Take Ownership" does not show up in my context menu for the desktop.
​

 

[Ztruker]

You need to right clik on something you want to take ownership of (folder or file), then it should show.

 

[pheonix73]

You need to right clik on something you want to take ownership of (folder or file), then it should show.

I downloaded, and installed, Add_Take_Ownership.reg, but as I said before, "Take Ownership" does not show up in my context menu for the desktop.

As I said, "Take Ownership" does not show up in my context menu. The only way to get to that context menu IS to right click on something.

Here's a screen shot:

 

[andrew129260]

Go to Local disk C\ users Right click on your user profile folder

Does take ownership show up now?

Did you try restarting? If it still did not show up, that is very odd. Works everytime on every pc I ever tried it on.

 

[pheonix73]

Go to Local disk C\ users Right click on your user profile folder

Does take ownership show up now?

Did you try restarting? If it still did not show up, that is very odd. Works everytime on every pc I ever tried it on.

OK. It worked on my user profile folder. Will that correct the issue I am having (not being able to save created documents to my desktop)?

 

[andrew129260]

It should.

If it continues let us know.

I also suggest this:

Please Run sfc /scan now using option 2 in this tutorial: SFC /SCANNOW Command - System File Checker

Please post back the results.
Please indicate what message was displayed at the end:

Windows found no integrity violations

OR

Corrupt files were found, and windows was unable to fix them.

OR

Corrupt files were found, and windows successfully repaired them

 

[pheonix73]

It should.

If it continues let us know.

I also suggest this:

Please Run sfc /scan now using option 2 in this tutorial: SFC /SCANNOW Command - System File Checker

Please post back the results.
Please indicate what message was displayed at the end:

Windows found no integrity violations

OR

Corrupt files were found, and windows was unable to fix them.

OR

Corrupt files were found, and windows successfully repaired them

I'll do that, but I'm going to wait until the "Take Ownership" process is finished. It's been running for a bit now. Hopefully it'll be done soon.

 

[pheonix73]

It should.

If it continues let us know.

I also suggest this:

Please Run sfc /scan now using option 2 in this tutorial: SFC /SCANNOW Command - System File Checker

Please post back the results.
Please indicate what message was displayed at the end:

Windows found no integrity violations

OR

Corrupt files were found, and windows was unable to fix them.

OR

Corrupt files were found, and windows successfully repaired them

So far, "Take Ownership" has not worked to solve the problem. I'm running the SFC scan now. I will report back when it is finished.

 

[pheonix73]

It should.

If it continues let us know.

I also suggest this:

Please Run sfc /scan now using option 2 in this tutorial: SFC /SCANNOW Command - System File Checker

Please post back the results.
Please indicate what message was displayed at the end:

Windows found no integrity violations

OR

Corrupt files were found, and windows was unable to fix them.

OR

Corrupt files were found, and windows successfully repaired them

"Windows Resource Protection found integrity violations". Here is what it found:

2014-07-28 02:01:51, Info CSI 00000044 [SR] Cannot repair member file [l:30{15}]"winload.exe.mui" of Microsoft-Windows-BootEnvironment-OS-Loader.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-28 02:01:51, Info CSI 00000046 [SR] Cannot repair member file [l:34{17}]"winresume.exe.mui" of Microsoft-Windows-BootEnvironment-OS-Loader.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-28 02:01:52, Info CSI 00000048 [SR] Cannot repair member file [l:22{11}]"winload.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 6.1.7600.16757, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-28 02:01:52, Info CSI 0000004a [SR] Cannot repair member file [l:26{13}]"winresume.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 6.1.7600.16757, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-28 02:01:54, Info CSI 0000004b [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:30{15}]"winload.exe.mui" by copying from backup
2014-07-28 02:01:54, Info CSI 0000004c [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:34{17}]"winresume.exe.mui" by copying from backup
2014-07-28 02:01:54, Info CSI 0000004e [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\windows\System32\en-US"\[l:30{15}]"winload.exe.mui" from store
2014-07-28 02:01:54, Info CSI 00000050 [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\windows\System32\en-US"\[l:34{17}]"winresume.exe.mui" from store
2014-07-28 02:01:55, Info CSI 00000051 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:22{11}]"winload.exe" by copying from backup
2014-07-28 02:01:55, Info CSI 00000052 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:26{13}]"winresume.exe" by copying from backup
2014-07-28 02:01:56, Info CSI 00000054 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:22{11}]"winload.exe" from store
2014-07-28 02:01:56, Info CSI 00000056 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:26{13}]"winresume.exe" from store


I am running it again to see if it will fix them by running it a second time.

 

[pheonix73]

After running sfc /scannow a second time, this is the result I received:

2014-07-28 02:01:51, Info CSI 00000044 [SR] Cannot repair member file [l:30{15}]"winload.exe.mui" of Microsoft-Windows-BootEnvironment-OS-Loader.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-28 02:01:51, Info CSI 00000046 [SR] Cannot repair member file [l:34{17}]"winresume.exe.mui" of Microsoft-Windows-BootEnvironment-OS-Loader.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-28 02:01:52, Info CSI 00000048 [SR] Cannot repair member file [l:22{11}]"winload.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 6.1.7600.16757, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-28 02:01:52, Info CSI 0000004a [SR] Cannot repair member file [l:26{13}]"winresume.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 6.1.7600.16757, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

 

[MilesAhead]

Third time may be a charm.

 

[andrew129260]

We can also get someone to look at the log

 

[Ztruker]

Install and run SURT then try sfc again:

See here: What is the System Update Readiness Tool?

The System Update Readiness Tool can help fix problems that might prevent Windows updates and service packs from installing. For example, an update might not install if a damaged system file prevents the update from recognizing the version of Windows that's running on your computer.

If your computer is having problems installing an update or a service pack, download and install the tool, which runs automatically. Then, try installing the update or service pack again.

Good information here: How to Analyze the System Update Readiness Tool CheckSur.log File

 

[pheonix73]

Third time may be a charm.

The third time I ran it, there were no errors, but, I still can not save documents or notes to my desktop.

 

[Ztruker]

Can you create a new .txt file on the Desktop?

Right click, New, Text Document?

 

[pheonix73]

Can you create a new .txt file on the Desktop?

Right click, New, Text Document?

Yes, but when I type something, then try to save it, I get a message that says: "Please check if this file is opened in another program".