Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,586 posts in this topic

Recommended Posts

Advertisement

@Tetonne

 

well i am not sure what broke?!

 

I dont see FakeSMC in newer boot logs??? this must not be installed right?

 

1) was it the new dsdt.aml ?

2) was it the new kexts?  maybe issue as DSMOS doesn't arrive?

3) was it new clover 2133 -> 2165 ?

 

may you can replace each item - 1 at time on working configuration?

Share this post


Link to post
Share on other sites

Updated posted Clover b2184 for T420 at post #397

 

  • Clover
    • minor tweaks/refinements to config.plist (e.g. dont think darkwake is needed anymore)
    • has 2 OEM configs - 1 for high-res and 1 for low-res
    • Note: recommend use of ssdt.aml if it fits your cpu - seems to get a bit more out turbo mode (get 32x at times instead of 30x with just Clover Generate P/C states)
  • Revised DSDT
    • for Shutdown hang (thanks to TimeWalker75a)
    • for native ACPIPlatform kext - no need to rollback or patch AppleACPIPlatform.kext - can use unmodified v1.8 from 10.8.5 (see notes below)
  • Kexts
    • ​Updated AppleIntelE1000e.kext
    • Updated ACPIBatterManager v1.40 
    • Updated FakeSMC
      • includes modified ACPI/Plugin Info.plist to remove DISABLED features so FAN speed shows up in HWMonitor (with stock AppleACPIPlatform.kext) 

ACPI Notes:

 

You can remove any patched/rollback AppleACPIPlatform.kext now if you like... but you may want to keep it depending on your preference based on comments below. I am still looking into this issue of course.... not sure if the problem is with the new kext or a dsdt issue.

  • the new DSDT conforms (more) to the native unmodified kexts ACPI spec... so dont have to replace the AppleACPIPlatform.kext. 
  • native AppleACPIPlatform.kext v1.8 (10.8.5) works but seems to have some issues with Power button lights after wake.
  • native AppleACPIPlatform.kext v1.7 (10.8.4) works too - but does not wake as well when you have external eSATA/USB drives. But good news as the v1.7 does not seem to have power light issue.

If you choose not to upgrade to 10.8.5, this new DSDT and the kexts will work in 10.8.4 (or older.) 

Share this post


Link to post
Share on other sites

the last pack (T420-UEFI-Clover-b2184_10.8.5 ) works now :)

the guilty kext was AppleACPIPlatform.kext 10.8.5 so i use AppleACPIPlatform.kext 10.8.4

 

I deleted my previous posts to make the thread clearer

 

Thanks again for this great stuff

Share this post


Link to post
Share on other sites

@Tetonne

glad you got it working - you are welcome - et merci pour testing et feedback.

 

yeah, i am bit suspicious of the 10.8.5 v1.8 AppleACPIPlatform.kext myself and may rollback to the previous rev 1.7.  

 

EDIT: even with the slow blinking light problem after wake-up, v1.8 AppleACPIPlatform seems to be more reliable for me. doesn't  hang up (yet?) like it 1.7 did from time to time - with the fast flashing light when going to sleep and never waking up! 

 

IMO, 10.8.5 with new 8-bit changes in the DSDT overall has made it work better than ever.

Share this post


Link to post
Share on other sites

@All

 

Haven't been on in a while. Life, you know...

 

You guys have made outstanding progress in the few weeks I haven't checked in. In the coming days, I will try to catch up with you 420 guys. Gendalo hasn't been on in a while, so I think I'll be on my own for a little while. And I see Kogen hasn't been on in a while either. I was going to ask if he could add "/430" to the thread title or maybe a mod could do it. I want to attract more 430 users to this thread. I really don't want to break it out into its own thread because the hardware is so similar and you guys have provided (although inadvertently) all the info needed to get this working for us 430 guys.

 

Just want to reiterate my appreciation for all of your work. This is really the only solid, worthwhile 430 hack resource.

Share this post


Link to post
Share on other sites

In the meantime before Mavericks is GA....

 

2 things addressed in the post  #397  for 10.8.5 and T420

 

  1. There was an patch for 10.8.5 (v 12F45) today. I downloaded with App Store and update no problem ... other than it replaced AppleHDA and Bluetooth stuff. So you will need to replace those items! (latest kexts are in the zip)
  2. I added some code in the DSDT to fix the LED issue I had upon wake up. That is where the LED keeps pulsing as if it was still asleep and the moon on the lid stayed on too. now it just resets them to power light steady on and moon off.  so now i am much happier with 10.8.5 ACPI. 

 

Update 4-Oct-2013

  • Revised DSDT
    • for Shutdown hang (thanks to TimeWalker75a)
    • for native ACPIPlatform kext - no need to rollback or patch AppleACPIPlatform.kext - can use unmodified v1.8 from 10.8.5 (see notes below).
    • made a change/fix to reset LEDs upon wakeup.
  • Updated Clover to b2165 b2184
  • Updated AppleIntelE1000e.kext
  • Updated FakeSMC
  • Updated VoodooPS2Controller
  • Added Patched AICPUPM kext for Chameleon compatibility.

Share this post


Link to post
Share on other sites

Tluck-
I got problems when using the vanilla AppleACPIPlatform.kext.
I extracted the kext from the 10.8.5 update using Pacifist. How do you get it?
See attached screenshot of the errors. I had these errors also the other day when I tried to use the vanilla kext.

  
Any ideas?
 
Thanks,
AJ

post-121087-0-13069800-1380927827_thumb.jpg

Share this post


Link to post
Share on other sites

@AJ -

 

 i got the v1.8 AppleACPIPlatoform.kext when i upgraded to 10.8.5. are you 10.8.4 or 10.8.5? The 10.8.0-10.8.4 version AppleACPIPlatoform.kext is 1.7

 

are you talking about SMC errors? i am not totally sure but what version of FakeSMC are you on?

 

are you using the new dsdt?

Share this post


Link to post
Share on other sites

I'm on 10.8.5 and I got your latest FakeSMC and dsdt from today's pack...

The error comes when I use the new AppleACPIPlatoform.kext v1.8. I just had to put back v1.7 to be able to boot...

Share this post


Link to post
Share on other sites

hmm. not sure what to say!? do you get these SMC errors when using the v1.7? are you using the patched version from the 10.8.4 clover bundle? or the standard 10.8.4 v1.7 ?

Share this post


Link to post
Share on other sites

I don't get the SMC errors when using v1.7, it only happens with v1.8.

I believe I am using the patched version of v1.7, it was coming from your previous packs...

Share this post


Link to post
Share on other sites
attached are 3 AppleACPIPlatform kexts - can you test the v1.7 unmod?

 

v1.7 unmod

v1.7 ermac patch

v1.8 unmod

 

these are the only non-apple kexts...

 



$ kextstat |grep -v apple
Index Refs Address            Size       Wired      Name (Version) <Linked Against>
   16    2 0xffffff7f811a1000 0x16000    0x16000    org.netkas.driver.FakeSMC (877) <9 7 5 4 3 1>
   17    0 0xffffff7f811b7000 0x4000     0x4000     org.hwsensors.driver.CPUSensors (877) <16 7 5 4 3>
   30    2 0xffffff7f80811000 0xe000     0xe000     org.rehabman.voodoo.driver.PS2Controller (1.8.8) <9 7 5 4 3 1>
   31    0 0xffffff7f811be000 0x6000     0x6000     org.hwsensors.driver.ACPISensors (877) <16 9 7 5 4 3>
   34    0 0xffffff7f81d16000 0x6000     0x6000     org.rehabman.driver.AppleSmartBatteryManager (1.40) <9 4 3>
   40    0 0xffffff7f80e72000 0x1b000    0x1b000    com.insanelymac.driver.AppleIntelE1000e (2.5.4) <39 10 5 4 3 1>
   52    0 0xffffff7f80834000 0x5000     0x5000     org.rehabman.voodoo.driver.PS2Keyboard (1.8.8) <30 28 7 6 5 4 3 1>
   53    0 0xffffff7f8081f000 0xb000     0xb000     org.rehabman.voodoo.driver.PS2Trackpad (1.8.8) <30 28 7 6 5 4 3 1>

ACPIPlatform.zip

Share this post


Link to post
Share on other sites

Yes, I have copied the latest one from your pack today...

 

aj:~ aj$ kextstat | grep -v apple
Index Refs Address            Size       Wired      Name (Version) <Linked Against>
   19    0 0xffffff7f809cf000 0x1e000    0x1e000    com.rim.driver.BlackBerryUSBDriverInt (0.0.67) <18 17 16 14 13 5 4 3 1>
   22    2 0xffffff7f80ebc000 0x16000    0x16000    org.netkas.driver.FakeSMC (877) <9 7 5 4 3 1>
   23    0 0xffffff7f80ed2000 0x4000     0x4000     org.hwsensors.driver.CPUSensors (877) <22 7 5 4 3>
   37    0 0xffffff7f80ed9000 0x6000     0x6000     org.hwsensors.driver.ACPISensors (877) <22 9 7 5 4 3>
   39    0 0xffffff7f816d3000 0x6000     0x6000     org.rehabman.driver.AppleSmartBatteryManager (1.40) <9 4 3>
   42    2 0xffffff7f808ae000 0xe000     0xe000     org.rehabman.voodoo.driver.PS2Controller (1.8.8) <9 7 5 4 3 1>
   53    0 0xffffff7f808d1000 0x5000     0x5000     org.rehabman.voodoo.driver.PS2Keyboard (1.8.8) <42 34 7 6 5 4 3 1>
   54    0 0xffffff7f808bc000 0xb000     0xb000     org.rehabman.voodoo.driver.PS2Trackpad (1.8.8) <42 34 7 6 5 4 3 1>
   79    0 0xffffff7f81a98000 0x1b000    0x1b000    com.insanelymac.driver.AppleIntelE1000e (2.5.4) <74 10 5 4 3 1>
   87    0 0xffffff7f81b1e000 0x4000     0x4000     com.globaldelight.driver.BoomDevice (1.1) <86 5 4 3 1>
  106    3 0xffffff7f81d4e000 0x43000    0x43000    org.virtualbox.kext.VBoxDrv (4.2.18) <7 5 4 3 1>
  107    0 0xffffff7f81d91000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (4.2.18) <106 51 13 7 5 4 3 1>
  108    0 0xffffff7f81d99000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (4.2.18) <106 7 5 4 3 1>
  109    0 0xffffff7f81d9e000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (4.2.18) <106 5 4 1>

Share this post


Link to post
Share on other sites

my feed back

test last pack (serial would be great to identify with pack we're talking about) with

FakeSMC20130706 +

AppleACPIPlatform kexts 1.8

 

​same issue as described here (same as with last pack in fact)

back to last pack (same as above) with include Fake SMC and AppleACPIPlatform v1.7 ermac patch

 

i suggess T420-UEFI-Clover-20131005-2184_10.8.5

 

Update : shut down is very long here

Share this post


Link to post
Share on other sites

@Tetonne  - thanks for testing. i will put ErmaC's patched AppleACPIPlatform.kext in the 10.8.5 bundle as an option for those that need to rollback. It was/is in the 10.8.4 pack. I am not sure why i can run the vanilla kexts?  i tested the old DSDT before splitting into 8bit variables and i can run 1.7  and 1.8  - just dont get battery info. with the new dsdt i can run all 3 versions. The new v1.8 works best and seem to consistently supports esata - before it was hit or miss.  yesterday i bumped up to rehabmans FakeSMC. 

Share this post


Link to post
Share on other sites

I found a fix for very low input volume of the AppleHDA LineIn/ExtMic I have been always experiencing.

 

While spending quite a few hours trying to rename LineIn to ExtMic, I noticed that one of the configuration widgets in the patched version of AppleHDA had been put in the wrong section.

 

The attached file has the following patch. If you have a compatible version of AppleHDA, it should be as simple as dropping it into the appropriate location in the AppleHDA kext, reboot, and your LineIn Mic should be much louder. Otherwise, you may need to make the edits yourself to Platform.xml, and then compress it to Platform.xml.gzip using the `Script RevoGirl AppleHda.zip` from e.g. http://olarila.com/forum/viewtopic.php?f=18&t=2676

--- /Backup Extensions/10.8.2_mods/AppleHDA.kext/Contents/Resources/Platforms.xml 2012-11-26 13:54:20.000000000 -0500
+++ Platforms.xml 2013-10-05 18:38:53.000000000 -0400
@@ -1574,38 +1574,12 @@
  <integer>20</integer>
  </dict>
  <dict>
- <key>Amp</key>
- <dict>
- <key>Channels</key>
- <array>
- <dict>
- <key>Bind</key>
- <integer>1</integer>
- <key>Channel</key>
- <integer>1</integer>
- </dict>
- <dict>
- <key>Bind</key>
- <integer>2</integer>
- <key>Channel</key>
- <integer>2</integer>
- </dict>
- </array>
- <key>MuteInputAmp</key>
- <false/>
- <key>PublishMute</key>
- <true/>
- <key>PublishVolume</key>
- <true/>
- <key>VolumeInputAmp</key>
- <true/>
- </dict>
  <key>NodeID</key>
  <integer>24</integer>
- </dict>
- <dict>
  <key>Boost</key>
  <integer>3</integer>
+ </dict>
+ <dict>
  <key>NodeID</key>
  <integer>27</integer>
  </dict>

Also nice, is enabling Ambient noise reduction. This is done simply by copying the SignalProcessing section from Mic to LineIn, in layout12.xml

 

Finally, and somewhat related, I wrote a script to parse CodecVerbs and pretty print the output for consumption in various places. For example, you can get your ConfigData section from

/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHardwareConfigDriver.kext/Contents/Info.plist and inspect it as follows:
./pinconfig.py -v -d -
                    AZccMAGXHRABlx4hAZcfAQG3HCABtx0QAbce
                    gQG3HwEB9xxAAfcdAQH3HhAB9x+QAjccoAI3
                    HQECNx6gAjcfkAG3DAI=
^D
"PinConfigurations",
Buffer(0x44)
{
0x30,0x10,0x21,0x01, /* 0x19        jack, External Rear,  HP Out, 1/8" stereo/mono,    Black, misc 0,                      , 3-0 */
0x20,0x10,0x81,0x01, /* 0x1b        jack, External Rear, Line In, 1/8" stereo/mono,    Black, misc 0,                      , 2-0 */
0x40,0x01,0x10,0x90, /* 0x1f    internal, Internal  N/A, Speaker,          Unknown,  Unknown, misc 0,  Jack Detect Disabled, 4-0 */
0xa0,0x01,0xa0,0x90, /* 0x23    internal, Internal  N/A,  Mic In,          Unknown,  Unknown, misc 0,  Jack Detect Disabled, a-0 */


}


< 01971c30 01971d10 01971e21 01971f01 01b71c20 01b71d10 01b71e81 01b71f01 01f71c40 01f71d01 01f71e10 01f71f90 02371ca0 02371d01 02371ea0 02371f90 01b70c02 >
'\x01\x97\x1c0\x01\x97\x1d\x10\x01\x97\x1e!\x01\x97\x1f\x01\x01\xb7\x1c \x01\xb7\x1d\x10\x01\xb7\x1e\x81\x01\xb7\x1f\x01\x01\xf7\x1c@\x01\xf7\x1d\x01\x01\xf7\x1e\x10\x01\xf7\x1f\x90\x027\x1c\xa0\x027\x1d\x01\x027\x1e\xa0\x027\x1f\x90\x01\xb7\x0c\x02'
AZccMAGXHRABlx4hAZcfAQG3HCABtx0QAbcegQG3HwEB9xxAAfcdAQH3HhAB9x+QAjccoAI3HQEC
Nx6gAjcfkAG3DAI=
 
 

Platforms.xml.zlib.gz

layout12.xml.zlib.gz

pinconfig.py.gz

Share this post


Link to post
Share on other sites

Awesome. yeah i gave up too after trying for hours (days?) to get ExtMic in the config! i will incorporate into AppleHDA for 10.8.5. thanks! 

 

works great - i just dropped in. i completely forgot thats why i bought a USB headset since when i used my iPhone buds/mic the input volume was so low! just tested again it seems to be louder!

 

thanks.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By ErmaC
      Slice is glad to present a new EFI bootloader.
      CLOVER
      Now version 2 rEFIt based.


      It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
      I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
      http://cloverefiboot.sourceforge.net/

      Main features:


      If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
      Continued by blackosx and STLVNUB.
      CloverGrower Downloads Installation How to do UEFI boot How to use - common words Calculator for Automatic DSDT fix Instructions for GraphicsInjector ATIConnector patching Any kexts patching with some Samples CustomEDID Hiding unnecessary menu entries Instruction for DSDT corrections to do DeviceInjection works Development Themes About kexts injection Instructions for P- and C-states generator Patching DSDT to get Sleep working CPU settings and geekbench ACPI tables loading DSDTmini Custom SMBios F.A.Q. iCloudFix Using mouse. How to make orange icons to be metallic How to make software RAID (by Magnifico) How to modify InstallESD.dmg (by shiecldk) Config.plist settings Using extra kexts and skipping kernelcache Choosing EFI drivers Configuration files Automatic config.plist creating Custom DSDT patches How to do sleep/wake working with UEFI BOOT DeviceID substitution (FakeID) Using Custom OS Icons Hibernation Floating regions Error allocating pages while starting OS -----------------
    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By Averyfreeman
      Dear @tluck 
       
      I have a T460s 20F9-003HUS - I5-6300U 2C 2.4GHz, FHD non-touch, 8GB DDR4, PM961 NVMe, vPro, AMT, etc.
      http://psref.lenovo.com/Detail/ThinkPad_T460s?M=20F9003HUS
       
      I have been following the following thread to hackintosh my T460s:
       but it's very long and hard to sort through, so I thought I'd start a new thread specifically for this issue
       
      Personally, my model has been doing pretty good with just the T460 EFI from github.  I did run the scripts to create and patch a new DSDT, though, after installing patchmatic and iasl.  I also manually installed VooDooPS2Controller.kext by following the guide on RehabMan's git wiki. 
       
      I also re-installed my kexts from CLOVER/kexts/other using kext helper to build them into the kext cache
       
      My only glaring issue is the touchpad.  It's unusably bad, I've had to use a mouse which kinda sucks on a laptop.
       
      It'll be really slow and then all of the sudden be really fast.  It hangs and skips intermittently.  Kind of hard to describe but it's {censored}. 
       
      So far I've tried: 
       
      installing latest version of VooDooPS2Controller, urning off all gestures, modifying speed, patching DSDT with autogen scripts (iASL, patchmatic). 
       
      Has anybody seen this problem?  What do you recommend I do?  
       
      Happy to provide any logs anyone believes would be relevant via pastebin, etc. 
       
      Thank you!
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
×