OOBEKEYBOARD, user name errors on Win 10 22H2

R

rd221122

New Member
Messages
7
Reaction score
1
What have I deleted or disabled to NOT allow me to enter the keyboard and my user name on a fresh installe.

When I try to enter each, i get something about OOBE.
 
Please attach your preset, after removing any user passwords or license key.
 
I ran into this problem while using someone else's preset for testing, and when I asked the same question (link) the community felt the culprit was likely the Scheduled Task of TextServicesFramework/MsCtfMonitor being disabled.
 
I don't see anything obviously wrong with this preset. Are you using Rufus or another tool which adds its own Unattended settings?
 
I use PowerISO to burn the ISO. I tried Rufus once, but would not boot. I will try Hellbovine's suggestion and try BurnAware to burn the ISO.

This is for a 32 bit Win 10 Installe for a laptop. Thanks again for the help.
 
I tried my 6th attempt at this. I disabled TextServicesFramework/MsCtfMonitor per Hellbovine's sugestion. I still have problems. what I get is,

Something went wrong you can try again, or skip for now
In yellow text OOBEREGION
OOBEKEYBOARD
Who's going to use this PC. Can not enter name. Keyboard does not work.

This is a 32 bit Windows 10 22H2 ISO downloaded from Microsoft.

I have a 64 bit version of the same, and it works great.

I can burn the 32 bit version to disc with no NTLite fixes. and it works. so it is something that I am disableing that is causing these errors.

A copy of take 6 preset is attached.
 

Attachments

Scheduled Task \Microsoft\Windows\CloudExperienceHost\CreateObjectTask is required for OOBE. Don't disable it.

+nuhi, this one should get a red warning from Apply.
 
I got rufus to work. Set CloudExperienceHost\CreateObjectTask to default. It was set to disable when I found it, and it worked.

Thank you very much for the help.
 
rd221122 said:
I am out of DVD's for now.
Click to expand...
Another member recently commented about using DVDs for testing too, so I wanted to ask what the reasoning behind this choice is, instead of pasting the files into a USB and installing Windows that way--to both speed up the install process and save DVD media.
 
Last edited:
I was unable to get Rufus to to boot to the OS. even with the USB as the first boot device. I figured out what I was doing wrong and all is fine now with the USB installation. I always preferd CD/DVD's for a long term archive. I didn't think I would have this much trouble with the 32 bit 22H2 Win 10....I didn't know that you can just copy and paste the ISO to a USB drive without some third party program . I'll try the copy and paste method. All of this moding an OS with NTLite, Intsalling on USB drives, is new to me, but I'm learning.
 
Yeah, it's a lot to take in at first, but pace yourself and before you know it you'll have a custom Windows. There's guides on the forum that walk users through much of it, such as this one (link), which goes through the steps of downloading an ISO, preparing a USB for Windows installation, and basic NTLite usage. After that, it's up to each individual user how far they want to go in their tweaking, and the advanced guides help with that.
 
garlin said:
Scheduled Task \Microsoft\Windows\CloudExperienceHost\CreateObjectTask is required for OOBE. Don't disable it.

+nuhi, this one should get a red warning from Apply.
Click to expand...
I just ran into this problem while 'Lite'ing a Win10 LTSC variant. In my case, disabling the Task CloudExperienceHose gave an error message during (attended) install of OOBE REGION.

Now, per garlin, the current message for this Task in NTLite is simply "Component: Out-of-Box-Experience."

Might I suggest that the (warning) message be stronger? Something like "Required for Installation. (OOBE.) May be disabled Live after Windows is installed."

(It seemed to me that it was safe to disable this Scheduled Task in the wim since 1) I wasn't hooked up to the Internet during installation and 2) I was never going to use the Cloud Experience. But I was wrong.)
 
It's a common user mistake to misjudge a Windows function by its canonical feature name (CloudExperienceHost). That's why various Compatibility protections exist, but that feature doesn't currently protect the Services/Extended Services.
 
pmikep said:
I just ran into this problem while 'Lite'ing a Win10 LTSC variant. In my case, disabling the Task CloudExperienceHose gave an error message during (attended) install of OOBE REGION.
Click to expand...
This service is mandatory during install for calling MS servers even you create a local account and part of WAAS.
 
Or use a full "unattended" installation, and no need this task, etc... (Out-Of-Box Experience can be removed)
And no requests during installation
 
You must log in or register to reply here.
Back
Top