Windows 10: start up error

How can fix autoIt Error Line 0 file C:\Users\65875\AppData\Roaming\ServiceGet\vapihas.dat"

:)

 

Unable to boot; 0xc000000f error on start

@axe0 - No, there was no file mentioned, although the error code remained the same. After I used the bootsec.exe /nt60 command the File: boot/bcd line appeared, which can be seen in the photos.
@zbook - I'll try what you have suggested and post the results. As for the assigned drive letters, no I don't know why they already have assigned letters. As far as I can recall, those were in fact the drive letters they were assigned when the computer was working, but I didn't reassign them during the troubleshooting process. The steps I had already taken are listed in the original post. I had tried to rebuild the BCD previously, but with the same results (i.e. didn't have access, system not found etc.)

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account?

The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join.

Thoughts?

 

Error: No work available to process

Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

At least those steps will rule out problems from the WCG end.