-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix print management which uses mmc. #2185
Comments
Interesting. Do you know what version you installed? I just checked in my 23H2 VM where I definitely never touched anything regarding Print Management but the console opens without any problems using Win+R > printmanagement.msc |
This issue was marked as stale because it has been inactive for 7 days |
I'll have a look using standard ISO from Microsoft instead of ISO built using a UUPDump. |
Yes this seems to be issue with images made using UUP Dump scripts which I use to have latest updates integrated in the ISO and maybe some other Windows ISO creation tools. |
As this seems not to be directly related to winutil, I'm going to close the issue. If you manage to isolate the issue and link it to winutil, please reopen the issue and we will be happy to help you :) |
Is your feature request related to a problem? Please describe.
If you clean install windows 11 and try to find print management management console, you wont find it util you uninstall print management using DISM and install it back using DISM, because when you are installing it using optional features in settings it'll fail every time you try.
Describe the solution you'd like
Fix print management automatically when either starting WinUtil or as one of the optional tweaks.
Describe alternatives you've considered
Doing it manually but that will start to get annoying quite fast when you have to install OS on multiple computers.
Additional context
I found solution in this article https://answers.microsoft.com/en-us/windows/forum/all/print-management-for-windows-11/e7fd45f0-ab9a-4b68-9142-ec18d7fd0da3 in response from RobinsonSilvestre
The text was updated successfully, but these errors were encountered: