Problems saving .doc and .txt files to my desktop

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 18
    Windows 7 Home Premium (64bit)
    Thread Starter
       #11

    andrew129260 said:
    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.
      My Computer


  2. Posts : 18
    Windows 7 Home Premium (64bit)
    Thread Starter
       #12

    andrew129260 said:
    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.
      My Computer


  3. Posts : 18
    Windows 7 Home Premium (64bit)
    Thread Starter
       #13

    andrew129260 said:
    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.
      My Computer


  4. Posts : 18
    Windows 7 Home Premium (64bit)
    Thread Starter
       #14

    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
      My Computer


  5. Posts : 5,092
    Windows 7 32 bit
       #15

    Third time may be a charm.
      My Computer


  6. Posts : 4,566
    Windows 10 Pro
       #16

    We can also get someone to look at the log
      My Computer


  7. Posts : 6,285
    Windows 10 Pro X64
       #17

    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
      My Computer


  8. Posts : 18
    Windows 7 Home Premium (64bit)
    Thread Starter
       #18

    MilesAhead said:
    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.
      My Computer


  9. Posts : 6,285
    Windows 10 Pro X64
       #19

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

    Right click, New, Text Document?
      My Computer


  10. Posts : 18
    Windows 7 Home Premium (64bit)
    Thread Starter
       #20

    Ztruker said:
    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".
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:44.
Find Us