User privileges insufficient to start a low level driver что делать

Обновлено: 17.05.2024

It seems that you know the group policy “Log on as a service” can achieve your goal, so I would like to confirm what do you want to ask?

If you do not know the path of the group policy “Log on as a service” in domain, you may expend Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Log on as a service in GPMC.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Marked as answer by Arthur_Li Microsoft contingent staff Monday, February 21, 2011 2:30 AM

All replies

And I know how to do it in local GPO
When installing a service to run under a domain user account, the account must have the right to logon as a service on the local machine. This logon right strictly applies only to the local computer and must be granted in the Local Security Policy.

Perform the following to edit the Local Security Policy of the computer you want to define the ‘logon as a service’ permission:

1.Logon to the computer with administrative privileges.
2.Open the ‘Administrative Tools’ and open the ‘Local Security Policy’
3.Expand ‘Local Policy’ and click on ‘User Rights Assignment’
4.In the right pane, right-click ‘Log on as a service’ and select properties.
5.Click on the ‘Add User or Group…’ button to add the new user.
6.In the ‘Select Users or Groups’ dialogue, find the user you wish to enter and click ‘OK’
7.Click ‘OK’ in the ‘Log on as a service Properties’ to save changes.
Notes:

•Ensure that the user which you have added above is not listed in the ‘Deny log on as a service’ policy in the Local Security Policy.

Microsoft TechNet Forum Bandara

It seems that you know the group policy “Log on as a service” can achieve your goal, so I would like to confirm what do you want to ask?

Marked as answer by Arthur_Li Microsoft contingent staff Monday, February 21, 2011 2:30 AM

Problem is - if you use this GPO to grant a user the "log on as a service" right, it obliterates all the other accounts that previously had that right when the policy applies. On next reboot, all kinds of stuff mysteriously doesn't work.

How useless is that?

Once more into the breach, dear friends.

Has anyone found a solution for the above yet?

Problem is - if you use this GPO to grant a user the "log on as a service" right, it obliterates all the other accounts that previously had that right when the policy applies. On next reboot, all kinds of stuff mysteriously doesn't work.

How useless is that?

Once more into the breach, dear friends.

Ditto, corndog. I would like to simply "append" a few users or groups to this right. but I cannot find anything. The only other way to give my user the same level of privileges (and unfortunately a whole bunch more) is with domain admin. :(

> Problem is - if you use this GPO to grant a user the "log on as a > service" right, it obliterates all the other accounts that > previously had that right when the policy applies. On next reboot, This is why you do NOT grant privs to users, but to groups. Either domain groups or - even easier to manage - local groups. > Ditto, corndog. I would like to simply "append" a few users or groups . and for that purpose, simply add your users and groups to the one

Thanks for your response. Unfortunately, I am trying to avoid adding service (user) accounts to Domain Admins just to give them full access to machine, which happens to include logon as a service.

When I Generate RSOP data for my machine, there are no groups explicitly defined via GPO with the "Log on as a service" right. However, when I look in the Local Security Policy there are a number of local/virtual accounts listed ("NT SERVICE\ALL SERVICES", "NT VIRTUAL MACHINE\Virtual Machines, etc"). Therefore, I must assume that the only AD groups with this permission are builtin privileged groups which we should be avoided like the plague.

Is there absolutely no way to grant a user or group rights to "logon as a service" to a select number of machines, say, a group of web servers or SQL servers, and not OVERWRITE the default accounts and groups that those machines might natively grant this right to?

If not, the only remedy for this user (it happens to be the authentication credential for Languard 2015) is to add it to the Domain Admins group, then use GPO to DENY every OTHER right available, to get the same results that myself and so many other users are attempting to achieve.

FYI, the Languard Support documentation provides that this right should be granted via GPO, which we learned the hard way, will OVERWRITE all existing users/groups with the right to logon as a service. Every other service running crashed hard. but Languard worked great. ;)

initialization error "user privileges insufficient to start a low level driver"

I get this error since I installed the iLok license manager or it may be because I scanned my plugins the unsafe way. How do I fix this?

New comments cannot be posted and votes cannot be cast

Seems that general advice I found via a google search is right-clicking the installed file and selecting "run as administrator" in the properties menu compatibility tab. Alternatively your VST may need an update or there may be an update available for download from the vendor. Hope you get it solved.

Kyocera Drivers Patch Tuesday BSOD

2 2

Kyocera Drivers Patch Tuesday BSOD

Mods, if this post is against the rules, just remove it. I posted in the Megathread, but I wanted more warning out.

KYOCERA PRINTER DRIVERS

Getting BSOD on multiple systems of APC_INDEX_MISMATCH for win32kfull.sys when doing anything involving a Kyocera printer.

upgrading to a newer Kyocera driver did not work.

Using basic Microsoft PCL6 printer driver works. Of course, you lose any Kyocera specific features. Annoying, nonetheless.

This issue was confirmed across four computers. Open Notepad or some other program, and simply attempt to open the Print dialog.

Edit: I should clarify, I was using Type 3 KX Kyocera printer drivers on networked printers.

Edit 2: Type 4 usermode XPS driver does not cause this issue.

Edit 3: I’m deploying the KX V4 XPS driver on the few systems I have, since I can just do them by hand. Not sure how I feel uninstalling the security update.

Edit 4: I’m seeing comments that it is affecting brands other than Kyocera. Brilliant work, Microsoft.

Edit 7: removing the cumulative update as mentioned in numerous replies does fix the issue if alternative drivers aren’t an option.

Edit 8: In the link above (Edit 6), Microsoft has officially posted a workaround and estimates a fix in the coming week.

Edit 10: I have installed the patches on my systems, and the printing issue seems to be resolved.

New comments cannot be posted and votes cannot be cast

2 3 & 4 More

KB5000802 seems to be the culpit, removing it allows to print with KX driver again

Brilliant move from Microsoft to bundle all updates in a big monthly cumulative update. So now you have the choice to uninstall KB5000802 leaving your systems exposed to potential security vulnerabilities or installing it leaving your systems BSOD when printing.

Update: The update causing this issue (KB5000802) seems to have been withdrawn and is not offered for installation any more. However this does not help for systems which already got it.

Administrators will have to remove the update manually eventually. No fun if you run a managed environment with hundreds of affected machines.

Even worse, scripting the fix and running wusa.exe /uninstall /kb:5000802 /quiet will not work as the /quiet switch is broken in Windows 10 and will not work with uninstall. Thanks again Microsoft

I found a work-around using a powershell script. Hoping it does not have other side-effects. Tested on Windows 10 20H2 EN/DE (yes it matters as the dism output is localized, what a crap):

This script should uninstall only the last security update.

Note: You will have to live with a potential security issue unless Microsoft is going to re-release the update.

Primarily it is KB5000802 as you mention, but it is also being caused by 5000808 and 5000822 in my environment. I think there was another 1 or two but I have not encountered those and did not write them down in my notes.

All printers we have being affected are Kyocera using the KX V-8.1.1109 driver. So newest available driver does not resolve the issue.

Also, a word of caution when recommending the Kyocera V4 driver packs. These drivers look to only be XPS based and as such will drop all advanced functionality of you devices. If you use staple, box sorting and other finishing functions you may lose most if not all of those service when using that driver. Example being an 8001i Copier with a Mail Sorter, Collation and Staple finisher and the expanded paper side feeds. These functions lose their options from our printer when applying this driver type.

If you ever want to remove the driver to go back to you device specific driver, you have to nuke the printer and reinstall it on the hosting device. That is from what I have seen and have done so far.

The XPS based drivers will work fine, as long as you do not need those advanced functions.

Also, in case anyone may need the direct link to the driver packs,

Thanks, it works

It works, tyvm you save my workday!

Thanks! it works

Thank you it worked.

any chance we should hope for a microsoft fixed update or are we going to have to uninstall the KB and pause updates everywhere ..

Worked for me, thnx!

sir, may i ask how to remove it from your computer ? but mine is KB5000808

Which worked for me (even though my computer has the update):

- Uninstalling all drivers, fonts etc with the Kyocera app

- Installing the printer exclusively through the Windows management of printers

Microsoft Employee here.

If you run into APC_INDEX_MISMATCH BSOD, you can try these steps as a mitigation until Microsoft addresses it in the future -

Section 1 - Enable Direct Printing. This should allow 32bit apps to print on 64bit OS without crashing.

Identify the name of your printer. E.g., "Kyocera TASKalfa 820 KX"

Often times, apps like Acrobat and OpenOffice runs as 32bit apps and this should be enough to workaround around the problem until Microsoft addresses the issue. But this will not solve the problem for 64bit applications printing on 64bit OS, nor 32bit applications printing on 32bit OS.

Section 2 - Enable PrintIsolationAware appcompat fix to your printer. This should allow 64bit applications printing on 64bit OS and 32bit applications printing on 32bit OS without crashing.

Follow the directions from Microsoft to acquire the Application Compatibility Tookit.

Follow these instructions to use the Compatibility Administrator tool to apply the “PrinterIsolationAware” fix to the affected application

User privileges insufficient to start a low level driver что делать

Предложено в качестве ответа Иван Проданов Microsoft contingent staff, Moderator 25 января 2021 г. 12:42
Помечено в качестве ответа Иван Проданов Microsoft contingent staff, Moderator 11 февраля 2021 г. 21:44

Все ответы

Предложено в качестве ответа Иван Проданов Microsoft contingent staff, Moderator 25 января 2021 г. 12:42
Помечено в качестве ответа Иван Проданов Microsoft contingent staff, Moderator 11 февраля 2021 г. 21:44

Определил что если установить драйвер для подключения по USB установка идет корректно.

Читайте также: