在今天的帖子中,我们将通过概述可能的原因来解决,然后针对以下问题提供相应的解决方法;尝试复制时可能遇到的“文件系统错误”,然后将密码粘贴到(File system error)Windows 11/10UAC凭据对话框中。
(File)凭据(Credential)对话框中的文件系统错误
假设您尝试使用提升的权限启动应用程序。例如,您右键单击cmd.exe并选择Run as administrator。用户帐户控制(User Account Control)( UAC ) 对话框会提示您输入用户名和密码(prompts you for your user name and password)。您从源复制密码并按Ctrl+V组合键粘贴密码,然后您会收到以下错误消息:
This program does not have a program associated with it for performing this action. File System Error (-1073741189).
1073741189表示 1 如果UAC或用户帐户控制设置的注册表值更改或系统文件(System Files)损坏,则可能会发生此文件系统错误。
此外,如果您右键单击密码字段,您可以选择粘贴(Paste)的快捷上下文菜单不会出现。
您调查并注意到Consent.exe在问题发生时崩溃。
同意(Consent)。exe是启动用户帐户控制(User Account Control)( UAC ) 用户界面的文件,UAC 是(UAC)Windows的授权层。这是一个真实而安全的过程。
文件(File)系统错误映射到下表中的以下信息:
Code | Symbolic Name | Error Description | Header |
Hex | Dec |
0xc000027b | -1073741189 | STATUS_STOWED_EXCEPTION | An application-internal exception has occurred. | ntstatus.h |
凭据对话框“文件系统错误”的可能原因
在Windows 10(Windows 10)中故意阻止将剪贴板的内容粘贴到安全输入框中。但是,Consent.exe崩溃是一个软件问题。
Windows 引入了一项安全更改,可阻止从Winlogon桌面(也称为安全桌面(Secure Desktop))访问剪贴板。此更改可防止未经授权的用户查看剪贴板上的信息。例如:
- 授权(Authorized)用户 A 将一些信息复制到剪贴板,然后锁定计算机。
- 未经授权的用户 B 唤醒计算机(处于锁定屏幕)并启动“ 讲述(Narrator)人” > “讲述人帮助(Narrator Help)” 。从那里,未经授权的用户 B 可以将剪贴板内容粘贴到讲述人帮助(Narrator Help)中的文本框中 ,然后阅读剪贴板内容。
此更改的副作用是,默认情况下不再可能将信息粘贴到UAC提升的密码文本框中。
在Winlogon桌面上默认显示(Winlogon)UAC提示的原因是,没有非安全进程(例如,尚未以SYSTEM身份运行的进程)可以监视输入到UAC对话框中的密码或其他信息。
如何修复凭据(Credential)对话框“文件系统错误”
按照微软(Microsoft)的规定,要修复consent.exe 崩溃问题,请安装最新的Windows 10 累积更新(Update)。
但是,CU 仅修复了许可.exe 崩溃问题。粘贴密码以保护输入框仍然被阻止。
如果您希望能够将密码粘贴到UAC凭据对话框中而不会收到文件(File)系统错误,Microsoft提供了以下解决方法:
To work around this issue, use gpedit.msc to configure the UAC elevation prompt to display on the standard user desktop instead of on the Winlogon desktop. As soon as the password is copied and on the clipboard on the standard user desktop, any process that is running in that desktop can read that data in plain text. In effect, the potential security breach has already occurred with no need for any process to try to read the password information from a UAC dialog box.
Microsoft已验证,在Windows 10中实施的安全修复程序以强制从标准桌面到Winlogon桌面的正确安全边界是所需的行为,这可能会在未来版本的Windows中保持这种行为。
Hope you find this post helpful and informative enough!
File system error when pasting password in UAC credential box
In today’s pоst, wе will addreѕs by outlining the possible cause and then provide the corresponding workaround for the following іssue; “File system error” that you might encounter when you try to copy, and then paste a password into the UAC credential dialog box in Windows 11/10.
File system error in Credential dialog box
Let’s say you try to start an application by using elevated permissions. For example, you right-click cmd.exe and select Run as administrator. A User Account Control (UAC) dialog box prompts you for your user name and password. You copy the password from a source and press Ctrl+V key combo to paste in the password and then you receive the following error messages:
This program does not have a program associated with it for performing this action. File System Error (-1073741189).
1073741189 indicates 1that if the UAC or User Account Control Settings’ Registry Values are changed or the System Files are corrupt, this File System Error might occur.
Additionally, If you right-click the password field, a shortcut context menu where you can select Paste does not appear.
You investigate and notice that Consent.exe crashes when the issue occurs.
Consent.exe is a file that launches the user interface for the User Account Control (UAC), an authorization layer for Windows. This is a genuine and safe process.
The File system error maps to the following information in the table below:
Code | Symbolic Name | Error Description | Header |
Hex | Dec |
0xc000027b | -1073741189 | STATUS_STOWED_EXCEPTION | An application-internal exception has occurred. | ntstatus.h |
Possible cause of the credential dialog box ‘File system error’
Pasting the contents of the clipboard into a secure input box is intentionally blocked in Windows 10. However, the Consent.exe crash is a software problem.
Windows introduces a security change that blocks clipboard access from the Winlogon desktop (also known as the Secure Desktop). This change prevents unauthorized users from seeing information on the clipboard. For example:
- Authorized user A copies some information to the clipboard and then locks the computer.
- Unauthorized user B wakes up the computer (which is at the lock screen) and starts Narrator > Narrator Help. From there, unauthorized user B can paste the clipboard contents into a text box in Narrator Help and then read the clipboard content.
A side effect of this change is that by default it is no longer possible to paste information into the password text box for UAC elevation.
The reason why UAC prompts are displayed by default on the Winlogon desktop is so that no nonsecure process (for example, one that is not already running as SYSTEM) can spy on passwords or other information that is input into the UAC dialog box.
How to fix Credential dialog box “File system error”
As prescribed by Microsoft, to fix the consent.exe crashing issue, install the latest Windows 10 Cumulative Update.
However, the CU only fixes the consent.exe crashing issue. Pasting password to secure the input box is still blocked.
If you want to be able to paste the password into the UAC credential dialog box without receiving the File system error, Microsoft offers the following workaround:
To work around this issue, use gpedit.msc to configure the UAC elevation prompt to display on the standard user desktop instead of on the Winlogon desktop. As soon as the password is copied and on the clipboard on the standard user desktop, any process that is running in that desktop can read that data in plain text. In effect, the potential security breach has already occurred with no need for any process to try to read the password information from a UAC dialog box.
Microsoft has verified that the security fix that is implemented in Windows 10 to enforce the correct security boundary from the standard desktop to the Winlogon desktop is the desired behavior, and this will likely remain the behavior in future versions of Windows.
Hope you find this post helpful and informative enough!