Strange MDM Enrollments on fresh installation

So something occurred and my computer went into "S" mode.  After failing to fix this, i scrapped the thing and ran the disk cleanse from the msi bios.  I then partitioned the disk new, and fully formatted each partition on the disk.  I then applied windows 11 via the WIM file using dism /apply-image.  I ran bcdboot to setup the bootloader.  Then i rebooted.  At the normal place you can hit shift F10 to get a command prompt this wouldnt work.  I was able to ctrl-shift-esc to get a task manager, upon trying to run cmd.exe, it says this cannot run on your computer (still in s-mode).  after a cmos flash and a cold reboot i was able to get the thing installed.  i noticed an external key popped up in the forbidden certificates for secure boot.

 

After loading up windows, i seen DMClient.exe running.  Looking at the event logs i see event logs matching company computer logs 

 

MDM PolicyManager: During Inbox found bad enrollment (82965F5A-6C65-4B7A-8075-488FCCE07D4E) during merge. Requesting merge (1e05dd5d-a022-46c5-963c-b20de341170f). Deleting policies for the enrollment. Enrollment state is (Your file waiting to be printed was deleted.).

 

registry keys also matching 

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning\Agent  - currentevent 5  | this is taken from a computer fully enrolled and managed from intune.

also showing a AutpilotCorrelationVector 94+P9vQMMEiwOk2F.0

And hklm\software\microsoft\provisioning\diagnostics\autopilot and the value IsAutoPilotDisabled 0 

 

Now i dont think this is malware, but its malicious.  Is there a way to trace where i am sending and receiving MDM signals from?  If i could get the AAD domain i could report this to Microsoft as abuse of their enterprise device management solution.  This computer was fully built from components and was licensed with an OEM windows Pro key.  (imaging as windows home does not have any changes except there is no group policy editor, bitlocker, etc.  Strangely, while typing this the autopilotcorrelationvector key in hklm:\software\microsoft\provisioning\diagnostics\autopilot has been deleted.

 

If there is like any advice or help that you could offer i would be all ears.

 

thanks!

Hello and welcome to Bleeping Computer!

I am HelpBot: an automated program designed to help the Bleeping Computer Staff better assist you! This message contains very important information, so please read through all of it before doing anything.

We apologize for the delay in responding to your request for help. Here at Bleeping Computer we get overwhelmed at times, and we are trying our best to keep up. Please note that your topic was not intentionally overlooked. Our mission is to help everyone in need, but sometimes it takes just a little longer to get to every request for help. No one is ignored here.

To help Bleeping Computer better assist you please perform the following steps:

***************************************************

In order to continue receiving help at BleepingComputer.com, YOU MUST tell me if you still need help or if your issue has already been resolved on your own or through another resource! To tell me this, please click on the following link and follow the instructions there.

CLICK THIS LINK >>> https://www.bleepingcomputer.com/logreply/796557 <<< CLICK THIS LINK

If you no longer need help, then all you needed to do was the previous instructions of telling me so. You can skip the rest of this post. If you do need help please continue with Step 2 below.

***************************************************

If you still need help, I would like you to post a Reply to this topic (click the "Add Reply" button in the lower right hand of this page). In that reply, please include the following information:

• If you have not done so already, include a clear description of the problems you're having, along with any steps you may have performed so far.
  
• A new FRST log. For your convenience, you will find the instructions for generating these logs repeated at the bottom of this post.
  
  • Please do this even if you have previously posted logs for us.
  • If you were unable to produce the logs originally please try once more.
  • If you are unable to create a log please provide detailed information about your installed Windows Operating System including the Version, Edition and if it is a 32bit or a 64bit system.
  • If you are unsure about any of these characteristics just post what you can and we will guide you.
• Please tell us if you have your original Windows CD/DVD available.
  
• Upon completing the above steps and posting a reply, another staff member will review your topic and do their best to resolve your issues.

Thank you for your patience, and again sorry for the delay.

***************************************************

We need to see some information about what is happening in your machine. Please perform the following scan again:

• Download FRST by Farbar from the following link if you no longer have it available and save it to your destop.
  
  FRST Download Link
  
  
• When you go to the above page, there will be 32-bit and 64-bit downloads available. Please click on the appropriate one for your version of Windows. If you are unsure as to whether your Windows is 32-bit or 64-bit, please see this tutorial.
• Double click on the FRST icon and allow it to run.
• Agree to the usage agreement and FRST will open. Do not make any changes and click on the Scan button.
• Notepad will open with the results.
• Post the new logs as explained in the prep guide.
• Close the program window, and delete the program from your desktop.

As I am just a silly little program running on the BleepingComputer.com servers, please do not send me private messages as I do not know how to read and reply to them! Thanks!