locked
"This operation requires an interactive window station" error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    It's well-known error and since this year i've been suffering of it (

    http://social.technet.microsoft.com/Forums/en-US/w7itprosecurity/thread/e4c0680a-4ecc-4477-90e0-0252fced0079)

    Now same history with realtek audio driver.

    Tell me how correctly to apply full qualified bug submit related to that error because i have no possibility to reinstall system

    =========

    I need more extended log like that available on Vista:

    from this tutorial

    • Edited by icegood Friday, November 30, 2012 4:32 PM
    Friday, November 30, 2012 4:21 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    Don't know exactly where was problem but at least i foubd workaround. Seems under system account only one permissions record proceed (at least for Windows 7 Home Premium)

    So, under administrator account i obtain:

    C:\Windows\System32\drivers>cacls .
    C:\Windows\System32\drivers BUILTIN\Administrators:(ID)F
                                CREATOR OWNER:(OI)(CI)(IO)(ID)F
                                NT AUTHORITY\SYSTEM:(OI)(CI)(ID)F
                                BUILTIN\Administrators:(OI)(CI)(IO)(ID)F
                                BUILTIN\Users:(OI)(CI)(ID)R
                                NT SERVICE\TrustedInstaller:(OI)(CI)(ID)F

    while under system account (thanks to Russinovich psexec!)

    C:\Windows\System32\drivers>cacls .
    C:\Windows\System32\drivers BUILTIN\Administrators:(OI)(CI)R

    and it's terrible. I've run

    cacls . /P  NT AUTHORITY\SYSTEM:(ID)F

    under system and obtain system-only rights under system. Everything works now. It's terrible to write OS in that way! And more terrible to reinstall everything everytime without understanding what's going on.

    • Marked as answer by Cloud_TS Thursday, December 6, 2012 2:24 AM
    Sunday, December 2, 2012 10:43 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have better results with proper procedure of driver installing, namely using those from computer vendor.

    Saturday, December 1, 2012 8:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Now, i finally found myself at least reason of error. It's of course shame that there is no proffesionals, who might guide me in right way but at least i hope now you may to do so.

    So, problem seems really was with rights for C:\Windows\System32\drivers folder. At least setupapi.dev.log says:

    !!!  flq:                          Error installing file (0xe0000233)
    !!!  flq:                          Error 0xe0000233: Cannot copy to specified target.
    !    flq:                               SourceFile   - 'C:\Windows\System32\DriverStore\FileRepository\hdxsrsa.inf_amd64_neutral_a9495ae663198ed8\RTKVHD64.sys'
    !    flq:                               TargetFile   - 'C:\Windows\system32\drivers\RTKVHD64.sys'
         flq:                          {SPFQNOTIFY_COPYERROR}
         flq:                               {SPFILENOTIFY_COPYERROR}
         flq:                               {SPFILENOTIFY_COPYERROR - exit(0x00000000)}
         flq:                          {SPFQNOTIFY_COPYERROR - returned 0x00000000}
    !!!  flq:                          SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
    !!!  flq:                          Error 1459: This operation requires an interactive window station.

    So, it simply cannot copy file from own repository to that folder. SourceFile exists and under regular user it even copiable to drivers folder. And that's all what happens! And i pointed out in my previous thread that it might be reason. Why stupid windows masks it with noninformative "This operation requires an interactive window station" - it's other question that i don't want discuss. I only now want to know under which permissions those operations above are supposed to be done.

    For now my "drivers" folder have all permissions for System, Administrators, TrustedInstaller and Interactive objects.

    Also read-only for regular users. Owner is remaded to Administrators, all properties are transmitted for subfolders and files.

    Sunday, December 2, 2012 2:06 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Don't know exactly where was problem but at least i foubd workaround. Seems under system account only one permissions record proceed (at least for Windows 7 Home Premium)

    So, under administrator account i obtain:

    C:\Windows\System32\drivers>cacls .
    C:\Windows\System32\drivers BUILTIN\Administrators:(ID)F
                                CREATOR OWNER:(OI)(CI)(IO)(ID)F
                                NT AUTHORITY\SYSTEM:(OI)(CI)(ID)F
                                BUILTIN\Administrators:(OI)(CI)(IO)(ID)F
                                BUILTIN\Users:(OI)(CI)(ID)R
                                NT SERVICE\TrustedInstaller:(OI)(CI)(ID)F

    while under system account (thanks to Russinovich psexec!)

    C:\Windows\System32\drivers>cacls .
    C:\Windows\System32\drivers BUILTIN\Administrators:(OI)(CI)R

    and it's terrible. I've run

    cacls . /P  NT AUTHORITY\SYSTEM:(ID)F

    under system and obtain system-only rights under system. Everything works now. It's terrible to write OS in that way! And more terrible to reinstall everything everytime without understanding what's going on.

    • Marked as answer by Cloud_TS Thursday, December 6, 2012 2:24 AM
    Sunday, December 2, 2012 10:43 PM
  • Question
    Sign in to vote
    12
    Sign in to vote

    That didn't work.  Windows 10 here, anniversary update August 2016.

    I scoured the net trying to find a solution and nothing worked until I combined several tips.  Posting it in case it helps others. This avoids the need to do a painful Windows reset:

    Google for "take ownership REG" and download the install and install the .reg files for that. Double click the install one to install it.  It adds the command Take Ownership to the context (right click on file or folder) menu.  (This avoids the need to take ownership manually and not forget to select child objects).
    Turn off firewall/AV for a few minutes
    Go to each of the following folders, right click them, and click the new Take Ownership option (created by the above):
        C:\Windows\system32/drivers
        C:\Windows\system32/driverstore
        C:\Windows\system32/DRVSTORE

    Then right click on each folder, Advanced, and set Full Control for all the accounts shown.

    Then you can double click the uninstall for the Take Ownership script if you don't want to have it anymore.

    That fixed it for me. It was affecting several unrelated driver installs.

    • Proposed as answer by Daniel_Harris Friday, August 12, 2016 7:34 PM
    Sunday, August 7, 2016 1:23 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Thank you for this post - It fixed my problems with the drivers, after upgrading to the Anniversary Edition of Windows 10.

    I used the registry keys for "Take Ownership" from this website:

    http://www.howtogeek.com/howto/windows-vista/add-take-ownership-to-explorer-right-click-menu-in-vista/

    Thank you :-)

    Monday, August 8, 2016 8:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had the exact same error on a Windows Server 2012 Standard machine when trying to install a printer across a network. It appears to be a damaged or unavailable driver. Installing the latest driver from the manufacturer on the print server (machine sharing the printer) fixed the issue.

    I hope this helps someone else :)

    Tuesday, August 9, 2016 12:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The solution almost worked for, but I had to change a few things.  First the reg method either failed or was insufficient.  Another step: Right-click folders drivers+driverstore+DRVSTORE, choose properties, security tab, advanced, On the popup (top) is a Change Ownership setting, I used that to make additional changes. And all changes must apply to subfolders. I had to do it twice. The second time an apply-to-folders checkbox appeared. I did that again to claim ownership.  Then start changing permissions.  I probably made many more changes than necessary. I noticed later there was an inherit checkbox and button -- didn't get to use that. Gots lots of error messages (ignored hem).  So no way to tell anyone what worked and what didn't.  But I was able to start updating my drivers fairly quickly. Good luck. Now to correct all my settings to what they're supposed to be.
    Monday, August 15, 2016 3:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Wow it actually worked for a smard card reader that stopped working after anniversary update of windows 10, thanks.
    Wednesday, September 14, 2016 12:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    THANKS VERY MUCH ZELYTS!

    Had a problem with my MS keyboard ever since the <g class="gr_ gr_50 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="50" id="50">anniv</g> update and set it aside for months, as nothing I'd found or tried would resolve it.  Your suggestion worked perfectly though!  Much appreciated. All the best for 2017!

    Sunday, January 8, 2017 5:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you. This process solved the issue for me on Windows Build 14986.
    Sunday, January 22, 2017 2:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Downloading the latest driver and installing it (after uninstalling the device) solved my problem.
    Sunday, July 30, 2017 7:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Very old post but I just wanted to say I just had this issue on Windows 10 and the log actually had the cause: "Not enough disk space"

    I don't know why Windows is being dumb and giving me a completely nonsensical error message and then throwing the correct error in the log. This is terrible design.

    Friday, October 12, 2018 6:58 PM