Windows 10: Hope I didn't 'Brick' my PC!

That showed up on the fresh install from the 'Media Creation Tool' download, (after cleaning up from my 'train wreck'!) *Wink
It's not un-installable either, I'd have to delete the .exe! A left over from the previous install maybe? Could you post the location of the exe file? I'd like to see if its on my system. I don't see it listed in Turn Windows features on off. Just to confirm, this is showing up in your Windows 8.1 install correct?

 

Gimme a minute to go over to Windows 8... *Wink

 

The Control File is in System32:

 

I don't have that file, I have embeddedapplauncher.exe and EmbeddedAppLauncherConfig.dll. That's an MSC file, I do believe that is a Microsoft Snap In. That's a bit out of my expertise level. I asked for more info because this the first I've heard of this Embedded Lockdown Manager. The Embedded part just doesn't make sense on your regular version of Windows? I'm no IT Pro though so a lot of things that don't make sense to me. Is it causing you any issues?

EDIT: Looks like I do have that file, I just looked on the wrong PC. See my other post later in this thread.

 

Naw, no issues.
I'll delete the shortcut, that's good enough! *Smile

 

Looks like a piece of missed un needed code that should be removed from the retail SKUs

Now available: Embedded Lockdown Manager update for Windows Embedded 8.1 Industry - Windows Embedded Blog - Site Home - MSDN Blogs

If it's still operatable in the normal retail it may be of use in commercial operations to lockdown and control user options - like a super group policy editor to cover modern apps *Wink

Edit, the last paragraph in the link states it's available as an option on retail SKUs so I suppose it's in case you want to run a touchscreen PC as a kiosk device and lockdown the charms etc

 

I just noticed something interesting? On my desktop PC that has Windows 8.1 Pro installed from my MSDN ISO, there is no trace of this Embedded Lockdown Manager. However, on my laptop which is running 8.1 Pro, installed with Media created by the Media Creation Tool, its there and usable. I wonder what else is different between the two? And why its included on one but not the other?

 

Is the laptop touchscreen? only reason that jumps out at me given the use of the panel *Confused

 

No touchscreen, just a touchpad. I am going to be doing a clean install of 8.1 Pro on my desktop in the next day or two. I plan on using the Media Creation Tool ISO. I'll make note as to whether the Embedded Lockdown Manager is installed or not.

 

I just did a clean install of 8.1 Pro on my desktop PC with install media created with the Media Creation Tool. The Embedded Lockdown Manager is there now. And that was before any Windows updates were done.

 

Yes, its in the install.wim - even core single language has it.

Rather strange, unless it will be used to disable charms and other desktop specific functionality... have to wait and see.

 

As near as I can tell it doesn't effect anything, its just there if you want to use it. I'm not sure really what its for. I'll have to research it a bit. I launched it briefly, by accident, and then just closed it again. I didn't look at it for much more than a second. I only looked for it after Edwin mentioned it.

 

It seems you would need to connect to another device running embedded and then you could use it to disallow ctrl+alt+delete etc on that device. It will not do anything on normal windows install.
Embedded Lockdown Manager (ELM) Technical Reference (Standard 8)

 

It seems you would need to connect to another device running embedded and then you could use it to disallow ctrl+alt+delete etc on that device. It will not do anything on normal windows install.
Embedded Lockdown Manager (ELM) Technical Reference (Standard 8) Makes me wonder why it was added? It's not something the average Windows user is going to need or use?

 

I have a feeling it is an omission - it should have been removed before the ESD file was loaded to the file server.

Ever since using Embedded Standard 7 to create Thin Client versions of Windows 7, I realised that the Windows developers must be using a modular OS building tool, like the IBW and ICE - perhaps just the same ones, but with the normal Windows branding etc. - in order to push through all the new builds of Windows 8, and now, Windows 10.

So it is not unreasonable to find a bit of code or a file left behind, or in this case, an executable intended for a server or development version, that may have not been intended for release - keep watching for it to disappear!