Iwanted to test something in Diagnostic startup mode. For some reason upon reboot, my PC showed my account picture with an error saying "Something happened and you PIN isn't available. Click to set up you PIN again." When I click on Set up my PIN, there is a pause, then I get the same message again. When I click on it again, I often get a dialog window saying "Search for app in the store" but if I choose yes, nothing happens.
I didn't try the other answer because it seemed super risky to move .exe files in System32 around, but I found another solution that only involves disabling the "pin-only" sign-on via RegEdit in Windows Recovery mode. This is I think a much less risky solution (and worked for me). Full credit to ramava on LTT for figuring this out. I'm pasting that answer below verbatim in case the link above breaks eventually:
This happened to me last night and I want to document it here so thathopefully someone else won't have to spend 3 hours trying to fix itthrough trial and error, or worse, have to "Reset my PC" or reinstall,which I was very close to doing before I solved it. Then later, Irecreated the problem on a virtual machine of a fresh Windows 10install to see which thing I did actually fixed it and discoveredanother potential problem that people may encounter. This may notsolve the problem completely if it was originally caused by somethingdifferent than my problem, but hopefully it'll be a good head startfor those people.
The problem is caused by a sign-in setting for Microsoft accounts inlater builds of Windows 10 that prevents you from using a regularpassword to logon, but doesn't work at all if the services that makeWindows Hello work aren't running. This setting is enabled by default.
For me, this happened because I enabled Diagnostic Startup inmsconfig. This disabled all the required services and then I couldn'tlogon because the only account on the computer was made using aMicrosoft Account instead of a local account.
You may be asked to log in at this point, which I think depends onyour which build of Windows it is. It did use the password and didn'tseem to have any trouble on the one machine that required me to do it.The much newer preview build never asked for one.
This will bring up the registry for the recovery environment (WinRE),not your install of Windows. So you have to manually load the registryhive to be able to edit them. To do that, first selectHKEY_LOCAL_MACHINE, then select File -> Load Hive... from the menu.
The hive files will be in C:\Windows\System32\config (or in the caseof one of my computers, it was E:). Load the SOFTWARE hive file. Itwill ask you for a name. I normally just use an extra s in front ofthe name, but it really doesn't matter as long as it's not somethingthat's already there. This will give us a new listing under HKLM. Myinstructions will assume you name them ssoftware and ssystem like Ido.
Go to HKEY_LOCAL_MACHINE\ssoftware\Microsoft\WindowsNT\CurrentVersion\PasswordLess\Device. There there is a key forDevicePasswordLessBuildVersion. Change the value from 2 to 0. Thiswill turn off that "Require Windows Hello" setting.
Based on comments above (for which I thank you) it seems that Selective Startup is not a problem, even if I cannot figure out why my PC is Selective Startup rather than Normal Startup. Since my PC is running well, I think the best course of action is to leave well enough alone.
The General tab of System Configuration (msconfig) shows my Dell Inspiron / Win 10 Pro v21H2 machine uses Selective startup, but the Boot tab indicates this is likely because I have Macrium Reflect Free installed. When I created my Macrium rescue media (e.g., a bootable USB thumb drive) as instructed I also added the Macrium Reflect rescue environment to my Windows boot menu. Now when I boot up my computer I see a screen with a 10 second countdown that allows me to boot normally into Windows (the default) or enter the Macrium Reflect recovery environment directly without having to boot up from my USB thumb drive.
I had the same trouble and if you go to the advanced button on the boot tab where you had the greyed out box, just click on the debug box that is currently unchecked. That will make the debug port box available and you can uncheck it, then uncheck the debug box and press ok. Seemed to fix my issue.
The idea is I click a button and it starts msconfig for me. Problem is when I run it on a x64 machine it crashes with a Win32Excpetion was unhandled error saying it can not find the file. I know the file exists in C:\Windows\System32\ and I believe this is related to my project being compiled for a x86 CPU type.
How can I rewrite the code so that it starts msconfig.exe on a 64 bit computer? I do not want to change the CPU type for building it. The idea is that I can run this program on either a 32 or 64 bit Window 7 machine and it works just the same.
It seems that the only way to avoid this issue is by changing the build type. See -0566-4eb9-b1e1-c591476a4958If anything it seems that maybe looking into the File System Redirector could provide some insight or a workaround!
This works around the problem that the file system redirector swaps the System32 folder for x86 apps because you start an x64 app that you do know exists 'msconfigstarter.exe' which can then access msconfig.exe because the system32 folder is not redirected for it.
Actually I've been having problems with this. Saying OSX isn't Windows is not a solution, since even Linux has this utility. It feels like a huge oversight or at the very least a design flaw due to the "it just works" philosophy of Apple. No, it doesn't just work, let me tinker.
My Mac Mini is extremely slow on start-up because of software that I have installed all wants to start at once : Adobe updater, Office updater, Flash updater, Creative Cloud, Onedrive, Dropbox, Plex, Chrome, etc.
Unless anyone can tell me the name of a built-in utility to manage startup programs, or at least a workaround that doesn't involve dredging through startup scripts, please don't leave your post here. I want solutions that I can use, not apple fanboy rhetoric.
Just because you don't get the answer you like, doesn't make the responses "fanboy". Statements like that will get you ignored. It's the same thinking as people pulling out the race card to make it all about them.
And yes, "it's not Windows" is a completely legitimate comment. It isn't, plain and simple. The only things that are similar are launching apps, creating and saving/closing files and folders, copying such items and other actions that are the same no matter which OS you're using. Underneath, there's no similarity at all. You can't make OS X do everything the same way Windows does any more than Windows can be forced to behave exactly the same way OS X does.
Yes and no. Saying that in a context where a utility isn't present due to system limitations or differences is totally valid, but using that as a reason as to why the utility shouldn't exist in the first place is asinine. Mac OS X is an operating system that gets bogged down just like any other. Microsoft gives me a way to strictly control ALL my programs and services at boot time, the same should be true for OSX. Saying "OSX isn't Windows", in the context it was used, was "fanboy rhetoric". Correct me if I'm wrong, but these support forums are here to help users get real help (some of them who switched from Windows to OSX, and can only refer to utilities by their windows counterparts), not to be scolded and told that they're wrong and that OSX doesn't work that way. I know very darn well how OSX works internally, probably better than you and that guy up there, I just don't keep up with shell updates and system utilities. But I digress.
Adobe does a great job hiding startup items. Like where did they put the function that automatically checks for updates? It clearly launches and loads with the OS, but where is it? There's nothing in the Creative Cloud panel preferences that allows me to turn it on or off.
I wasn't scolding anyone. I was simply stating facts. OS X is not Windows. Linux is no different. If there's something you need to that is specific to Red Hat Linux, then that's the one you have to use. No other variation of Linux will have that tool, and you can't force the behavior into another version.
Adobe's poorly designed but industry standard software can make people frustrated. I must apologize. I have no idea how they can even hide a startup item like that; even the MS Office updater was on that list - but not Adobe's.
At the same time, utilities can be duplicated, even though OS features may not. Linux varies greatly between distributions but I'd be hard pressed to find a utility that hasn't been at least somewhat successfully duplicated in at least one other distribution. I'm not really asking for a core OS feature, just a catch-all startup and services list utility. It would prove supremely useful, especially with companies like Adobe.
I completely agree. Apple though has always maintained very tight control over the OS. It intentionally limits what you can do as far as modification, or turning functions on/off. This can be both a good thing, and a bad thing. Power users hate it, but it helps prevent novices from making changes that prevent the OS from working as it should, or even starting up if they really overdo their digging.
Msconfig is a tool that allows you to manage the startup and system settings of your Windows computer. With msconfig, you can control which programs and services launch when you start your computer, troubleshoot startup problems, and make changes to the system configuration.
By using msconfig, you can easily control which programs launch automatically when you start your computer. To do this, you can open msconfig, go to the "Startup" tab, and uncheck the programs that you don't want to start automatically. This can help you speed up your computer's startup time and reduce the number of unnecessary programs running in the background.
3a8082e126