gleep52

No one else has this problem or knows why this is happening?

I am using hyper-v to build a windows 7 image (installed from scratch MVL disc), installed all of the windows updates, then using a windows 10 ADK boot file, I create the capture media and try to capture the image. This is how I've always done this in the past and it works fine with Windows 10. But so far I've tried this on three computers and each time the system runs it's sysprep, reboots, starts in PE, scans the volumes, then starts capturing them. But shortly into the second (OS partition) volume, it craps out and hyper-v just restarts for no reason, no warning, no ability to press F8 to open a log file because there is no warning, it just reboots/crashes... After it crashes chkdsk runs because of the unclean shutdown and it brings up a new computer as expected since sysprep was run. I have been building a windows 10 image simultaneously on the same hyper-v server host, righting to the same UNC path, with the same credentials, and the same capture media - no problems for windows 10 - just windows 7 that's crashing. Any words of wisdom? I can't find anything specifically identical to this crash issue...

Was a solution to this ever found? I'm having the same problem

Did you ever find out what the problem is here with this? I'm getting this on a lot of my older deployments... not sure what the deal is though?

Well at some point I was able to get past the winload.efi error by recreating my boot images - though I don't recall the process and since then something else has changed where the same winload.efi error is rearing it's ugly head again. I need to use uefi on these laptops, and it DID work previously. What version should my boot.wim file be? Mine says 6.2.9200.16384... isn't that the WinPE 4.0 version? When I try to add a boot.wim file directly from the windows media it fails. Google reveals others with the same issue and their work around was to use the boot images that came with WADK - but I don't know where those files are. Yes, I'm still noobish. Anyone able to throw out some help with this one?

We have CU2 installed and the update packages are in place - I've assigned them to our respective x86 and x64 container collections, however - when I go to the default push client - it still says the registered version is build .1000 instead of build .1300... how do I change that so it installs the latest version instead of depending on the upgrade each time? Is there a way? Or is this a normal/standard setup?

Anyone??

When we push out ANY of our images we've created with SCCM - it's hit or miss if the client will talk with SCCM properly. The client gets installed, the software center has our custom text on it, all the actions show up on the control panel on the client, everything looks absolutely normal, except updates never get pushed down, and endpoint does not install either. When looking at the config manager console, it shows the computer is there, but the client type is listed as "none" instead of "computer"... The client's control panel shows the right site code so I'm not sure what the hang up is. All the client actions are grayed out in the config manager console end, but if I use the remote control app and manually put in the computer name, it connects without any problems, just like it was fully registered by the site... I have tried uninstalling it, doing the wmi repairs, repairing the client install with right click tools, and found two registry patches to force the client out of provisioning mode, as sometimes the logs indicate that may be the problem. However, sometimes that is in the logs on machines that ARE working - so I'm not sure what to make of it - I only know that using these registry tweaks don't fix the problem either. When I do a single machine at a time (OSD) it usually works, but even then it's not 100%. If I do a group of computers at the same time, it hasn't worked right once yet. It works on a few, but not ALL the machines being imaged. FYI the reg tweaks commands (for x64 systems) are: REG ADD HKLM\SOFTWARE\Wow6432Node\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f REG ADD HKLM\SOFTWARE\Wow6432Node\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f Does anyone have any ideas for me? My boundaries are setup correctly as far as I can tell - I've tried it by IP and by AD site... same results either way. We're running SCCM 2012 SP1 CU2 and are trying to deploy win 8 pro x64 I'm pulling my hair out... any advice or support would be terrific. Thanks!

When I try to create a new task in the windows task scheduler, it fails with the error: An error has occurred for task <task name>. Error message: A task or folder with this name already exists. The strange thing is, I've got this happening on a lot of my servers now... I have no idea what I changed, but apparently I cannot create new tasks now - this is a brand new freshly installed windows box as well. On one of our servers, I have created many scheduled tasks, but I can no longer create new ones on that server either. We use SCCM 2010 SP1 as well, with endpoint protection - not sure if that's the culprit or not?? I could create scheduled tasks in task manager before SCCM, but I have no proof they are related. I tried creating a task on our domain controller, exporting it and then importing it on the desired server, but it gives the same error that a task or folder with that name already exists... there are NO tasks except the two that come with SCCM, and those are in the config manager subfolder. Does anyone know how to solve this? Or better yet, does anyone know how to hand out these tasks with SCCM? If I could do that - I'd be totally stoked. Thanks for any input you can provide and your time in helping with this problem!

We just got our sample unit in for our school district's next 300+ machines... it's UEFI - has legacy option in the bios. But if I switch it to legacy, the thing won't boot or do ANYTHING except stay at a boot manager screen (built in, not SCCM). If I switch it to UEFI, it boots normally, but if I plug in the Ethernet, it boots directly from it stating PXE boot IPv4... clever! Or is it? The WIM files load, but after the bar slides across the bottom, when it usually will start the server 2012 boot logo, instead it chirps and crashes. It says: Windows failed to start. A recent hardware or software change might be the cause. To fix it... <blahblah> File:\Windows\System32\boot\winload.efi Status: 0xc0000359 I'm still rather noobish with SCCM, but I added every driver I can find available for this laptop to the boot image, and it still fails to load the winpe environment. The laptop is by a company called M & A - the laptop is actually manufactured by Intel. Here's a link: http://macomp.com/Companion-Touch8.asp If anyone has some thoughts on why this is, or how I can overcome it - you'll forever be in my debt!

Thank you so much for posting your solution here. It didn't work exactly as you have listed for me, I had to do an extra sync between unselecting the classifications in SUP and running the reset command - but I did manage to get it working again thanks to you! Bravo!