Would someone help identify these quirks...

Jim

New Member
Messages
21
Reaction score
0
I've been crafting a "Lite" Windows 10 for a few weeks now. I'm ironing out the fine details but 2 particular things are giving me trouble.

* My integrated trackpad doesn't funtion (I2C HID Device & HP Wireless Button Driver inside Device manager have Yellow !)
- Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged.
* The "search" in the setting app doesn't generate results

Preset is attached. Any and all input is greatrly appreciated. I've been Trial and errorring. Hopefully someone can help me narrow my search.

Windows Build I'm editing...
Latest built UUPdump of "Windows 10 Enterprise 1809 x64 - 10.0.17763.7136"
 

Attachments

* My integrated trackpad doesn't funtion (I2C HID Device & HP Wireless Button Driver inside Device manager have Yellow !)
- Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged.

Restore the default I2C drivers, unless your PC has a specific driver set to download.
Code:
                <c>driver_iai2c.inf</c>
                <c>driver_ialpss2i_i2c_bxt_p.inf</c>
                <c>driver_ialpss2i_i2c_cnl.inf</c>
                <c>driver_ialpss2i_i2c_skl.inf</c>
                <c>driver_ialpssi_i2c.inf</c>

* The "search" in the setting app doesn't generate results

Restore Cortana:
Code:
                <c>microsoft.windows.cortana 'Cortana'</c>
 
  • Like
Reactions: Jim
garlin Thank you! You were the EXACT user I’d hoped would chime in. Swiftly too! Amazing. So, Cortana is also needed for search on 1809 as well? I read a thread that mentioned that but was convinced it was in later releases that required Cortana. I suppose I was incorrect. Also a huge facepalm on my part! I totally could’ve searched the XML I submitted for “I2C” Thought I tackled the I2C driver within NTLite. Not only with Host Machine protection but also manually scanning the Human Interface Device section as well.
Anyway, I appreciate the prompt reply. I feel novice for not identifying those swift findings!
 
Cortana is weird, because it doesn't do exactly the same features, depending on your W10/11 release. MS kept moving parts of Search around to different components. The other search component is the obviously named "Windows Search" (taskbar).
 
Again, a novice mistake! Cortana clearly states "Locked by compatibility: Shell Search" & "Depends on: Windows Search". I just didn't interpret that as Cortana is needed for Search. Anyway, thanks for the clarification. The notes within NTLite should've been enough for me to accomplish my missioin. I must have been brain f*cking it too hard!
 
Back
Top