Issues with Boot Images & PXE Booting Since SP1 Install

Question

Good Afternoon All - 
I recently updated to SP1, had some issues, but they got resolved.  Now, though, I'm having an issue booting to PXE as well as updating any boot images created
before SP1 was installed.  Booting to USB Bootable media using a newly created boot image seems to work fine. 
Boot Images
When I update my DPs for any of my boot images in SCCM, they fail and i get the below error:
  Error: The wizard detected the following problems when updating the boot image.
• Failed to install required components into the boot image
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"BBS0012F\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
I've even gone as far as removing all drivers from the boot image, but still get the same message.  I was able to create a couple of
new MDT boot images which seem to work fine, though.  I am not sure which log file is for boot images, but nothing appeared in distmgr.log.
PXE Booting Issue
After trying many things, I removed PXE config from my site and uninstalled WDS then started all over again.  Here's what I did and my results.  Please tell me what I'm missing...
After uninstall & server reboot, I enabled PXE + every option in DP tab in SCCM
It automatically installed WDS (same server) and added the two boot images I had checked for PXE use.  one x64 and one x86.
I checked my DHCP Scope whose values hadn't changed sine it worked (that I know of).  They are:
Option #66: 192.168.20.37 (SCCM Server/DP/PXE) 
Option #67 \boot\x86\wdsnbp.com.  I've tried \boot\x86\pxeboot.com as well as each of these with x64.
When I PXE boot from a workstation, I receive an IP, a bit of info, then it goes to Contacting Server....  When trying one of the boot files above, I was prompted for F12, but receved a blue screen with error.  When trying all other boot files,
they just hang at Contacting Server until they timeout.
I looked at SMSPXE.log and found something interesting...
The IDs for the two boot images I have assigned to PXE are ABC003B3 & ABC00B36.  In the smspxe.log, though, it keeps repeating "could not find boot image ABC0012F!  12F does exist and is a boot image,
but not the one I want to use by any means and does not have PXE checked.
I went ahead and checked 12F, updated DPs (which failed - see above); unchecked it; then updated the DPs again.  PXEBoot.log showed that it was trying to remove the 12F files from RemoteInstall which was a good sign.  I then restarted the WDS service
and tried PXE booting again.  Yet again, it failed and was still looking for 12F.
Any suggestions / Ideas???  Thanks!
UPDATE 1
I just changed option #67 to \smsboot\x86\pxeboot.com then restarted the WDS service.  I booted to PXE and this time was asked to hit F12.  I did so and it looked as if it would work.
Instead, I got a blue screen with the following error:
Recovery
Your PC needs to be repaired
The boot configuration disk contains errors or is missing 
file: boot\BCD
Error Code: 0x000000f
I think that it's the same error as before, but is blue instead of black due to new Win8ADK perhaps.  Thanks
Ben K.

Answer 1

Update 4
Sorry to make this the longest post ever :)
I just read that others with this error checked DISM.log.  I did so when running a DP update for the boot image and got the below errors:
2013-01-11 16:27:04, Info                  DISM   DISM Provider Store: PID=1636 TID=5104 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-01-11 16:27:07, Info                  CBS    Failed to find a matching version for servicing stack: C:\Windows\TEMP\BootImages\{DADCFE01-3557-4058-99CC-2A15EDF905AF}\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\
[HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-01-11 16:27:07, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-01-11 16:27:07, Warning               DISM   DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-01-11 16:27:07, Warning               DISM   DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-01-11 16:27:07, Error                 DISM   DISM Package Manager: PID=4104 The package WinPE-Scripting-Package is not applicable to the image. - CPackageManagerCLIHandler::Private_ProcessPackageChange
2013-01-11 16:27:08, Info                  DISM   DISM Package Manager: PID=4104  Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2013-01-11 16:27:08, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{DADCFE01-3557-4058-99CC-2A15EDF905AF}/mount/Windows/System32/config/SOFTWARE,
the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
(The above one appears 8 times - almost in a row)
2013-01-11 16:27:08, Error                 DISM   DISM Package Manager: PID=4104 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081e)
Help!  Thanks :)
Ben K.