Password protected EFI and Single User Mode

Hello Community,
if I protect the EFI with a password than the single user mode is disabled. But I thought that I can enter the single user mode by entering the EFI password but no password prompt appears. Only the possibility to change the startup volume is accessible by a password prompt. Do I miss a possibility or is the only way to enter the single user mode by bypassing or disable the password by using the firmware password utility on the installation disk without violence?
BTW: I know the act of violence by changing the RAM configuration but this isn't the way I want to describe in the system documentation
Thx in advance & Bye Tom
Message was edited by: prontosystems

Try holding the Option key while booting. It should ask for the password, then allow any boot options after you select the drive. If you boot from the install DVD (using the Option key and password), you can use the "Utilities" menu to disable the password, after choosing your language.

Similar Messages

Difference between emergency state and single user mode ?

Hi,
I want to know the difference between emergency state which we normally use in suspect mode database and single user mode.
Navakanth

Emergency/suspect mode is tells you the state of the database and database is not available for user action but where as single user mode tells the user action preference. Database is active and available for the user action.
You can refer
http://msdn.microsoft.com/en-us/library/bb522682.aspx
EMERGENCY
The database is marked READ_ONLY, logging is disabled, and access is limited to members of the sysadmin fixed server role. EMERGENCY is primarily used for troubleshooting purposes. For example, a database marked as suspect due to a corrupted log file can be
set to the EMERGENCY state. This could enable the system administrator read-only access to the database. Only members of the sysadmin fixed server role can set a database to the EMERGENCY state.
SINGLE_USER
Specifies that only one user at a time can access the database. If SINGLE_USER is specified and there are other users connected to the database the ALTER DATABASE statement will be blocked until all users disconnect from the specified database. To override
this behavior, see the WITH <termination> clause.
The database remains in SINGLE_USER mode even if the user that set the option logs off. At that point, a different user, but only one, can connect to the database.
Before you set the database to SINGLE_USER, verify the AUTO_UPDATE_STATISTICS_ASYNC option is set to OFF. When set to ON, the background thread used to update statistics takes a connection against the database, and you will be unable to access the database
in single-user mode. To view the status of this option, query the is_auto_update_stats_async_on column in the sys.databases catalog view.
If the option is set to ON, perform the following tasks:
Set AUTO_UPDATE_STATISTICS_ASYNC to OFF.
Check for active asynchronous statistics jobs by querying the sys.dm_exec_background_job_queue dynamic management view.
If there are active jobs, either allow the jobs to complete or manually terminate them by using KILL STATS JOB.
--Prashanth

Dont know the admin password, cant get into single user mode

I have recently bought a PowerMac G4 with a dual core 1.25GhZ processor on a car boot. I do not know the admin password, and i cant get in to single user mode. What to do?! Seems like it has Open Firmware Password Protection, what ever that is, and i have the discs and tried disabling it, but to do that you need the admin password. It's and endless loop! Help me please, i have no idea what to do now...

Disabling the Open Firmware Password
Open Firmware password protection can be bypassed if the user changes the physical memory configuration of the machine and then resets the PRAM three times (by holding down Command, Option, P, and R keys during system startup).
An Open Firmware password will provide some protection, however, it can be reset if a user has physical access to the machine and can change the physical memory configuration of the machine.
Mac OS X
Security Configuration
For Version 10.4 or Later
Second Edition

Won't boot normally or in recovery and single user mode, safe mode hangs up halfway

iMac locked up with visual glitches while playing the Mac beta client of League of Legends. Had to force a shutdown by holding the power button. Now it won't boot; after the Apple logo and spinning wheel I just get a white screen. I tried launching in recovery mode, that didn't work. Then I tried safe mode; the bar filled a little over half and then nothing but white screen. I was able to boot single user mode once; ran fsck -fy and rebooted, still white screen. Now I can't get back to single user mode. I booted with command option P R to reset the NVRAM and got the second chime, but still nothing.
Luckily all my important files are in the cloud, but I'm really hoping my computer isn't completely dead. I haven't had any issues in the past. I've even been playing LoL for over a month with no issues, until now when I tried to play the newer game types, Dominion and ARAM; both caused visual glitches forcing shutdowns. I was able to restart my computer with no problem after the first two visual glitches, but after the last one I am stuck at the white screen as I described above.
Thanks in advance for your help!

I'd bet the drive is damaged. You could try reformatting if possible. Again, you are booting from the Recovery-10.8.2 disk if you can. If you can't, then you will need to use the installer disc that came with the computer.
Install or Reinstall Lion/Mountain Lion from Scratch
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Erase the hard drive:
1. Select Disk Utility from the main menu and click on the Continue button.
2. After DU loads select your startup volume (usually Macintosh HD) from the
      left side list. Click on the Erase tab in the DU main window.
3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on
        the Security button and set the Zero Data option to one-pass. Click on
      the Erase button and wait until the process has completed.
4. Quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Install button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible
            because it is three times faster than wireless.

Screaming Fans ,10.4.3., and Single User Mode.

I wanted to add my experience with the screaming fan problem and 10.4.3.
When I ran Disk Utility and used the verify disk option I received some minor errors and proceeded to boot the OS X install disk and run Disk Utility from there. When I did I received no errors. Rebooted back to 10.4.3 and reran disk utility and received the same minor errors. So I read one of the Mac sites that stated that one needed to run in single user mode and execute fsck f. This where the fun started.
When I went into single user mode the fans went wild. But I knew this to be normal and proceeded with repairing the disk (which was successful as evident with no errors being reported while booted to the desktop and running live verify disk. But before I got to that point the fans remained screaming after the reboot to 10.4.3. I reset the PRAM and NVRAM but to no avail. The fans would not quite down. The fix turned out to be very simple I unplugged the computer (after shutting down) for about 15 seconds. Re plugged it in and it was fine after that. Fans back to normal! I replicated the problem applied the same fix and again every thing was normal.
I just thought I would pass this on to the iMac community.

Hi Steven, bit unclear on a couple things.
When I went into single user mode the fans went wild. But I knew this to be normal and proceeded with repairing the disk
Normal for fans to go wild in single user or when repairing the disk?
I replicated the problem applied the same fix and again every thing was normal.
The problem being screaming fan and the fix being resetting SMU? (unplug for 15secs). So how did you replicate it, and is it really fixed now?

10.4.3 and Single User Mode, now Wireless Keyboard can

Hello all.
IN case you haven't found out which I did, just to let you know, with the latest OS 10.4.3 update, now you can boot into Single User Mode (fsck) with your
b wireless keyboard
and still at the same time
b continue to complete fsck process with your wireless keyboard!!
No more switching to a regular wired keyboard just to complete the process!
Cheers

Hi Steven, bit unclear on a couple things.
When I went into single user mode the fans went wild. But I knew this to be normal and proceeded with repairing the disk
Normal for fans to go wild in single user or when repairing the disk?
I replicated the problem applied the same fix and again every thing was normal.
The problem being screaming fan and the fix being resetting SMU? (unplug for 15secs). So how did you replicate it, and is it really fixed now?

Disable single user mode

Is there a way to disable single user mode? I just booted in single user mode and w/o any password I changed my root password! In my mind this is a HUGE security hole, any one could gain root access to my laptop in a matter of less than a minute! I might as well not have a root password. I have the latest and greatest security updates, but this seems to be the biggest security risk in my mind.

If someone has physical access to your computer, your software is vulnerable in the way that you describe. There are a couple of approaches to preventing this problem. I have not tried any of this so I can only point you to some websites.
One way to prevent anyone booting into single user mode is to enable a password in Open Firmware, as described at Setting up firmware password protection in Mac OS X 10.1 or later. You would have to enter the password every time that you booted. And, you definitely would not want to forget your password; if you did, I don't know what you would have to do to recover.
A second approach is to use a 3rd party patch to prohibit casual use of the single-user feature. Look here for info on such a patch: Mac OS X Single User Mode Root Access. I believe that the software discussed here forces someone to type in a password to boot in single-user mode.
One question that I have about the second approach is whether it is possible for the patch to become out of synch with a future OS update. If that happened, one would also need a way to recover.
I hope this helps. If you are really concerned, I suggest that you do some internet searching on this topic.
Rich
EMAC G4 1.0 GHz Mac OS X (10.4.8)

HT1492 Single user mode not working.

Whenever I hit command-s to go into single user mode it doesn't work. I used to do it all the time to help my grandma who doesn't let me know her password, but always forgets it reset her computer. Please help!

Thank you! The thread you posted had my problem exactly, and the solution. It was the Macally keyboard, so I uninstalled the driver (and single user mode worked), and then I installed an older driver, so now my keyboard works AND single user mode works. If all of my computer problems could be so easy...

Single User Mode Question

I use single user mode to do fsck because doing it on a live disk takes way too long. I was wondering if there is a way to repair permissions from single user mode. Thanks

1. what does AFAIK mean?
As Far As I Know
2. What I have gathered is that it is near next to y difficult to repair permission fro the CLI and single user mode.
Correct. You can't use diskutil because the disk framework isn't loaded. You can do it if you're booted from an install DVD, though.

Why won't single user mode recognize /sbin/mount command?

I need help from people who are knowledgable abou these Mac wonders of the world and single user mode.
I'm trying for the life of me to run "memtest" in single user mode and am finding it impossible.
After I boot into single user mode, I get a "Shell>" prompt.
I type in /sbin/fsck/ -y to do some check thing. I then type in /sbin/mount -uw /
Both times I get an error saying that "/sbin/yada yada yada is not recognized as an internal or external command, batch or whatever"
No command work at all. I have no clue what I'm doing and am using instructions from where I got the memtest app. Sure I could just run it from the Terminal but then you're not testing all of the RAM, only the available portion. There's a huge chunck that won't be tested as OSX is using it. I want to do this as I just upgraded RAM to 8G with Crucial and now my MBP is acting very slow and weird.
HELP???? Why does this have to be sooooo hard.

I found the solution to the problem. Somone on a different forum had the same issue at one time. The problem is my use of Refit. When you hold Command-S at start when using refit you go into a single user type mode inside the refit shell. So it is something different.
Instead I needed to let the Mac boot Refit like normal. With the Mac partition highlighted press "F2" and it will display boot options for the Mac partition. One of them is Mac OSX single user mode. Simply select and hit enter and then I enter the correct single user mode and I'm off.
Then everything works like it should. I was my own undoing with my use of Refit.

Single User Mode Crash HELPPPP!!!

So, I just finished installing windows 7 build 7022, and using the modified bootcamp.msi to get all of the drivers installed.
I went to boot into OSX, and all that it does is sit on the grey apple screen while the gear spins, and spins, and spins.
I went into single user mode and this is the crash report that I got.
Process: securityd [51]
Path: /usr/sbin/securityd
Identifier: securityd
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1]
Date/Time: 2009-06-09 06:50:47.092 -0400
OS Version: Mac OS X 10.5.7 (9J61)
Report Version: 6
Anonymous UUID: 694D9F27-A097-484D-AEFD-A3C054CB5BBB
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000000
Crashed Thread: 4
Thread 0:
0 libSystem.B.dylib 0x912f4e5a getdirentries + 10
1 libSystem.B.dylib 0x912f4d94 readdir + 70
2 com.apple.CoreFoundation 0x92b3a1e0 _CFBundleCopyDirectoryContentsAtPath + 1264
3 com.apple.CoreFoundation 0x92b3eb59 _CFBundleURLLooksLikeBundleVersion + 57
4 com.apple.CoreFoundation 0x92b2f3af _CFBundleCreate + 287
5 com.apple.CoreFoundation 0x92b2f9ab CFBundleCreateBundlesFromDirectory + 187
6 securityd 0x0002dc34 0x1000 + 183348
7 securityd 0x0002c175 0x1000 + 176501
8 securityd 0x0000485f 0x1000 + 14431
9 securityd 0x00004633 0x1000 + 13875
10 securityd 0x00004564 0x1000 + 13668
11 securityd 0x00003eee 0x1000 + 12014
12 securityd 0x00003e0a 0x1000 + 11786
13 securityd 0x00002836 0x1000 + 6198
14 securityd 0x00011ff2 0x1000 + 69618
Thread 1:
0 libSystem.B.dylib 0x912d1292 machmsg_overwritetrap + 10
1 libSystem.B.dylib 0x91330dde machmsgoverwrite + 86
2 securityd 0x000041d4 0x1000 + 12756
3 securityd 0x0000a8f2 0x1000 + 39154
4 securityd 0x0000a8a0 0x1000 + 39072
5 libSystem.B.dylib 0x91302155 pthreadstart + 321
6 libSystem.B.dylib 0x91302012 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x913131fa pread$UNIX2003 + 10
1 com.apple.security 0x92c57f4f Security::Universal::typeOf(Security::UnixPlusPlus::FileDesc) + 49
2 com.apple.security 0x92c58dae Security::CodeSigning::MachORep::candidiate(Security::UnixPlusPlus::FileDesc&) + 26
3 com.apple.security 0x92c507f5 Security::CodeSigning::DiskRep::bestFileGuess(char const*) + 63
4 com.apple.security 0x92c50b4b Security::CodeSigning::DiskRep::bestGuess(char const*) + 299
5 com.apple.security 0x92c4ee1a Security::CodeSigning::KernelCode::mapGuestToStatic(Security::CodeSigning::SecC ode*) + 116
6 com.apple.security 0x92c517c4 Security::CodeSigning::SecCode::getStaticCode() + 24
7 com.apple.security 0x92c51611 Security::CodeSigning::SecCode::staticCode() + 33
8 com.apple.security 0x92c5a36f Security::CodeSigning::GenericCode::hostingPort() + 25
9 com.apple.security 0x92c5a548 Security::CodeSigning::GenericCode::locateGuest(__CFDictionary const*) + 24
10 com.apple.security 0x92c4e2d9 SecCodeCopyGuestWithAttributes + 51
11 securityd 0x0004a0ad 0x1000 + 299181
12 securityd 0x0004a2b0 0x1000 + 299696
13 securityd 0x00016f4a 0x1000 + 89930
14 securityd 0x00005584 0x1000 + 17796
15 securityd 0x00042900 0x1000 + 268544
16 securityd 0x00005396 0x1000 + 17302
17 securityd 0x00004d17 0x1000 + 15639
18 securityd 0x00004c84 0x1000 + 15492
19 securityd 0x00004282 0x1000 + 12930
20 securityd 0x0000a8f2 0x1000 + 39154
21 securityd 0x0000a8a0 0x1000 + 39072
22 libSystem.B.dylib 0x91302155 pthreadstart + 321
23 libSystem.B.dylib 0x91302012 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x912d1292 machmsg_overwritetrap + 10
1 libSystem.B.dylib 0x91330dde machmsgoverwrite + 86
2 securityd 0x000041d4 0x1000 + 12756
3 securityd 0x0000a8f2 0x1000 + 39154
4 securityd 0x0000a8a0 0x1000 + 39072
5 libSystem.B.dylib 0x91302155 pthreadstart + 321
6 libSystem.B.dylib 0x91302012 thread_start + 34
Thread 4 Crashed:
0 com.apple.CoreFoundation 0x92b5bc57 CFDictionaryContainsKey + 39
1 securityd 0x00019568 0x1000 + 99688
2 securityd 0x0001a46a 0x1000 + 103530
3 securityd 0x000333d4 0x1000 + 205780
4 securityd 0x00043a08 0x1000 + 272904
5 securityd 0x00059a32 0x1000 + 363058
6 securityd 0x00004d17 0x1000 + 15639
7 securityd 0x00004c84 0x1000 + 15492
8 securityd 0x00004282 0x1000 + 12930
9 securityd 0x0000a8f2 0x1000 + 39154
10 securityd 0x0000a8a0 0x1000 + 39072
11 libSystem.B.dylib 0x91302155 pthreadstart + 321
12 libSystem.B.dylib 0x91302012 thread_start + 34
Thread 4 crashed with X86 Thread State (32-bit):
eax: 0xa038c4ec ebx: 0x92b5bc3a ecx: 0x4d555458 edx: 0x00000010
edi: 0xbffffd7c esi: 0x00000000 ebp: 0xb0206cf8 esp: 0xb0206ce0
ss: 0x0000001f efl: 0x00010283 eip: 0x92b5bc57 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x00000000
Binary Images:
0x1000 - 0x9afff +securityd ??? (???) <0a5eeb92a410eb2d8ecf46c344180615> /usr/sbin/securityd
0xbc000 - 0xc8fe7 com.apple.pcsc 6.0 (34733) <a93011d49a6d04d6d35bfb526927f54d> /System/Library/Frameworks/PCSC.framework/Versions/A/PCSC
0x8fe00000 - 0x8fe2db43 dyld 97.1 (???) <100d362e03410f181a34e04e94189ae5> /usr/lib/dyld
0x90ba7000 - 0x90c04ffb libstdc++.6.dylib ??? (???) <04b812dcec670daa8b7d2852ab14be60> /usr/lib/libstdc++.6.dylib
0x912d0000 - 0x91437ff3 libSystem.B.dylib ??? (???) <b47c8e6e45aef620730710a732bf1930> /usr/lib/libSystem.B.dylib
0x91b18000 - 0x91ba4ff7 com.apple.framework.IOKit 1.5.2 (???) <97b9f9d584f48891377f0481b9104434> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x91d20000 - 0x91d27ffe libbsm.dylib ??? (???) <d25c63378a5029648ffd4b4669be31bf> /usr/lib/libbsm.dylib
0x91d28000 - 0x91d36ffd libz.1.dylib ??? (???) <5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib
0x92349000 - 0x92482ff7 libicucore.A.dylib ??? (???) <cac059ebdac7d9a63ee0f7a648c9f6cf> /usr/lib/libicucore.A.dylib
0x927c2000 - 0x928a2fff libobjc.A.dylib ??? (???) <7b92613fdf804fd9a0a3733a0674c30b> /usr/lib/libobjc.A.dylib
0x92b16000 - 0x92c49fef com.apple.CoreFoundation 6.5.6 (476.18) <2d52bab73660117571bd6486dc318f8e> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x92c4a000 - 0x92e1bffb com.apple.security 5.0.5 (36371) <c13e0bb1acfdcf94be4d3ee118ef190e> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x93017000 - 0x9301efe9 libgcc_s.1.dylib ??? (???) <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib
0x96db0000 - 0x96ddbfe7 libauto.dylib ??? (???) <42d8422dc23a18071869fdf7b5d8fab5> /usr/lib/libauto.dylib
0x97118000 - 0x9711cfff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
If someone can PLEASEEEEEEEEEEEEE help me, I would appreciate it!
Message was edited by: lysdexik

1. what does AFAIK mean?
As Far As I Know
2. What I have gathered is that it is near next to y difficult to repair permission fro the CLI and single user mode.
Correct. You can't use diskutil because the disk framework isn't loaded. You can do it if you're booted from an install DVD, though.

Does single user mode bypass password protection?

Does booting into single user mode bypass account password protection? From what I can see single user mode allows me to access the entire hard disk as root. Is this one of the reasons for open firmware password protection?

Unfortunately there is nowhere to put a padlock on the case of an iMac G5. Perhaps I will wrap it in a chain at night. I think it might spoil the design, unless Apple could release an iPadlock and iChain in a cool white with silver trim.
I have experimented with Filevault in the past and I have heard of the risks you describe - I may even have read the posts in question when I was researching it. I decided not to use it in the end, because the risks and extra login time weren't worthwhile for me.
I had thought that having a login password was sufficient to prevent access to my files on the machine, but now I know single user mode circumvents this. I think I may just save important files to an encrypted disk image.
I do encrypt my backup, though this prevents it from being bootable. I am currently working on having a minimal bootable partition plus an encrypted backup partition on my backup disk.

Hi, i forgot my macbook pro(snow leopard) password and i tried to reset it through single user mode, but whenever i type, everything comes out in CAPs instead of lower case. Each time i press the minus(-), it always comes out as an underscore(_).Pls help.

Hi, i forgot my macbook pro(snow leopard) password and i tried to reset it through single user mode, but whenever i type, everything comes out in CAPs instead of lower case. Each time i press the minus(-), it always comes out as an underscore(_).Pls help.

Well, you can try easing the shift key up with something thin but flexible (credit card sort of thing) but if the contacts below are stuck you may need to get it seen to by an authorised repairer.
If you can borrow a keyboard (a PC one will probably work as long as the password is alpha-numeric with no special characters) you can at least get in to backup your HD before going for repair.

Why can't I enter single user mode on my Mac Mini for an admin password reset?

Hi,
I recently created a new user account for my mac and deleted the old one, not realising that this was the only account with admin priveleges. As such, I no longer have access to administrator priveleges, and cannot grant them to my new user account.
I have tried to boot in single user mode and recovery mode but neither command results in any reaction on the part of my computer.
This thread follows on from a previous, unrelated disscussion:
BDAqua: If you hold alt key at bootup do you see a lock in the middle?
Yenots: No...what does this mean?
BDAqua: If it did, it would mean Firmware Password Protection was enabled, which prevents booting in other modes, so that's not the problem, are you using a wired Mac KB, or Windows KB?
Yenots: I'm using an 'Apple Keyboard with Numeric Keypad' [ http://store.apple.com/uk/product/MB110B/B/apple-keyboard-with-numeric-keypad-br itish ]
If you find me here BDAqua, hit me with your knowledge!
Any other contributions are welcome and, now we're under the right heading, will hopefully help other users who have encountered this problem.
Thanks, Cristo

Hi,
Thanks for the link to MacPilot, and the sexy screenshot. I found an archived version for 10.4 on the koingosw website. That solves getting into single user/safe mode. Though I'd be interested to see whether sudo nvram boot-args="-s" will result in single user boot.
As for creating administrator priveleges for my new user account, I've found a method which looks good:
     \single user mode\
     cmd-s
     \mount drive\
     mount -uw
     \open 'directory access'\
     lauchctl load /System/Library/LaunchDaemons/com.apple.opendirectory.plist
     \list users\
     ls /Users
     \change password\
     dscl . passwd /Users/<username> <password>
I think that this method intends that if I change the root users password I'll be changing the administrator password (as root is the only user with administrator priveleges), and subsequently be able to change my new user accounts priveleges using 'netinfomanager'. But I'm not 100%. Could you give me your opinion on this?
Furthermore, three keys 'L' 'O' and '(' aren't working on my keyboard, which means I can't try this until I find an intact keyboard to borrow. I was thinking maybe a mod version of the above instructions would work in terminal using sudo, so I could use the keyboard viewer to type the missing characters. If you have any ideas on constructing such a mod I would be interested to hear them.
Otherwise, Thank You for your help BDAqua! And enjoy your summer wherever you are.

Can't log in with valid password, can't boot from disk, can't access disk utility, in single user mode can't reset password as appears locked in caps mode with '?' for forward slash, can anyone help?

Can't log in with valid password, can't boot from disk, can't access disk utility, in single user mode can't reset password as appears locked in caps mode with '?' for forward slash, can anyone help?

Which keyboard layout you were using? German, French ... I suppose your layout is reset to the default: US and you are unable to find the "?" or "/" ...
Please have a look into the keyboard viewer, to see how the layout of your keyboard is actually.
marek

Password protected EFI and Single User Mode

Similar Messages

Maybe you are looking for