Windows 8.1 Boot Issues

I have Windows 8.1 Pro with all automatic updates successfully installed, running on:
Sabertooth Z77 motherboard
GEForce GTX 770 video
Intel i7-3770K LGA1155
Xonar DSX PCIE 7.1 audio card
Corsair TX850 power
16GB of Corsair Vengeance DDR3 DRAM
More than adequate cooling.
The machine has never been right from first build. It just doesn't boot reliably, often requiring 20+ minutes of reboot attempts, resets and random fiddling before it eventually starts. At first I thought the problem was Windows 8 famously not shutting
down properly. Certainly, Windows 8.1 has improved things. But it just won't boot properly and I'm at a loss what to do.
Here's what typically happens, but it's different every time and things are not necessarily in the below order:
1. POST always succeeds with no issues.
2. Windows 8 logo appears with circle of dots.
3. Screen goes black for a few minutes. HDD LED flashes like its life depends on flashing.
4. Monitor gets fed up and powers down.
5. HDD gets tired and has a break.
6. Monitor springs back to life, but only to show a black screen for a minute or two.
7. Windows 8 logo re-appears with circle of dots.
8. Screen goes black again.
9. HDD decides to have another go and flash like it's flashing in the Olympics.
10. (Not always!) Windows announces there is a problem booting (you don't say) and offers some help but:
a) The fix option refuses to accept the install DVD saying it's not valid
b) Enabling boot logging produces a 12KB log file full of space. Just space space space and no words or numbers at all.
11. Rebooting or resetting generally reproduces steps 1-10.
12. Just occasionally, I get a login screen, hence here I am posting this using the problem machine. When it boots, everything seems to work fine. No obvious issues with any hardware. Device Manager happily reports that all is well, except the SATA AHCI
controller didn't start - well, obviously it did start, or something to replace it did, or I wouldn't be here typing this - and neither did the "Multimedia Audio Controller" - although again, something else must be driving the audio because it's
working fine.
I did get a WHEA_UNCORRECTABLE_ERROR on screen during boot at one point (only once!), but I don't know how to get at the details and Googling it suggests I need to be a hardware vendor to get the explanation.
Er, now what? Anyone? Please?

Almost the same system as me except my MB is little better. Issue is most likely your bois settings. Boot from none uefi.
Disable all drives that you don't need to boot your system or choose none uefi , there will be options for this. Disable virtua, if you have it. Make sure your bios settings is achi format. If you setup windows in some other format like IDE SATA
you will have to most likely reinstall the os using achi format. If that is the case you will need to switch back to IDE sata in your bios.
Start with disabling all drives you don't need to boot from. That is including your CDrom
Edit: make sure your bios is up to date

Similar Messages

Windows 8 Laptop Boot Issue (and other related problems)

My Toshiba Satellite S855D-S5148 laptop was bought about a month ago, but it's been giving me issues for the last week.
The most significant one was a boot issue, where out of nowhere, the PC would not start, and after a hard restart, I received an error message saying Windows was not able to start. So I called tech support and they guided me through a PC refresh. That seemed to have solved the issue until twenty minutes later, when my system froze and I could not move the cursor let alone use any applications. So I did a hard restart again, and tried to do another PC refresh until the laptop 'clicked' and shut off. I restarted again, and my system seemed to be working normally until two days later (I did not shut it off or restarted it during this period, only kept it in hibernate when not in use).
Upon trying to use my laptop, it said Windows was reconfiguring. Afterwards, I received an error message saying that Windows had to restart due to 'this problem,' though the problem was not specified. The error message included a list of file addresses that presumably contained a description of the problem, but I can't access the files because they don't show up when I search their addresses. They are .dmp and .xml files, respectively.
Is anyone familiar with this problem? I wish I could return the laptop but it's a couple of weeks shy of the return period (Staples has a measely 14-day return period, but I didn't think I'd have to use it). I don't want to go through the hassle of shipping it off to Toshiba for repairs. Would reformatting the laptop solve the problem? I wish I could attach the .dmp and .xml files to this post but I can't locate them. I'd try using the recovery disks, but they were recently destroyed in a flood.
Any comments, advice, and/or suggestions are very much welcome!

Happy to learn the hardware is fixed.
I was told they could not do so without the product key. ... Any ideas as to how I can get my product key?
Everybody should know by now that there is no product key for preinstalled Windows. The OEM has it locked into the motherboard.
As I've said over and over, recovery media will restore the hard disk to its original out-of-the-box contents. Windows will be activated.
Windows is not installed during this process. Everything on the hard drive is restored. It's an important distinction.
-Jerry

P67A-GD65 (B3 ) & Windows 7 64Bit Boot Issue

Hi,
I feel the need to revisit this old forum post as I do not believe it has been fully resolved:
https://forum-en.msi.com/index.php?topic=156082.0
In summary the issue is "Most times the machine boots and performs flawlessly for hours, but often it boots with the Windows-7 “need to repair” screen and after running repair for a while Windows says: “Windows cannot repair the problem”…….but when I press the Reset button, the PC boots and runs just fine".
I only had the problem since updating from 1F beta 2 to the latest BIOS version. On the original forum thread there are some that had the view that the issue was introduced around BIOS version 1.F (full release, non-beta) and 1.G. Just to confirm this issue NEVER happened for me on 1F beta 2 or earlier BIOS releases. The original forum also has some people saying the issue did not exist on earlier BIOS versions as well.
Most people seem to have solved the issue by either resetting the CMOS or loading default BIOS settings. I tried this and it did initially solve the problem for me.
BUT when I installed new drivers (such as nvidia v301.24) or added new hardware (e.g. Bigfoot PCIe network gaming card) the problem came back.
This implies to me that there is an issue with the BIOS and that resetting the CMOS is a workaround rather than a true fix.
This leaves me with two choices:
- use an older BIOS, which is ok but limits me from the new functionality in the BIOS (including not being able to use certain hardware that the BIOS updates support)
- resetting the CMOS after loading new drivers or installing new hardware and then configure my settings (which is very tedious)
Neither option is ideal to me.
The main purpose of raising this issue is to ask whether MSI Support know of this issue and have it on their bug list to fix?
I am concerned it is not being addressed as other forum entries talk about BIOS version 1.K3 being the last version.
My system details are P67-GD65(B3), Windows 7 64bit, 16GB Gskill 2133Mhz memory, 2 SSD, 2HDD, Nvidia 570 GTX, Bigfoot network gaming card.

Quote from: momosala on 25-September-12, 22:19:54
Thank you _MELK_ for bringing us your experience.
It was already reported that this bug did not appear with older firmware versions.
It is interesting to know that version 1.14 does not have this bug.
This information should help the MSI support team to create a 1.K reliable firmware.
In my opinion, I do not think that Intel RST is the cause of this bug.
Sure thing momosala..
An update to this issue is as follow...
BIOS 1.14 fixed this issue completely. NO errors since I flashed back to it. I also reinstalled Intel RST without any issue either.
Note that I wanted 1.19 for another reason as well (fix for USB 3.0 port issues). I wound up flashing the chipset for the USB ports themselves instead . Now the MB works as intended! :D
WARNING: use the info below with CAUTION (not simple to do, and not provided/supported by MSI afaik)
INFO on USB 3.0 firmware/drivers -- again, use CAUTION and do your research before proceeding!
Note that it took me a few hours to complete the flash since I had to research which version of the chipset I had (hardware ID helped, LOTS of reading on the subject as well to find out HOW to flash my board properly).
You can find the drivers/firmware for the "Renesa USB 3.0 Host controller" by searching google for
Driver: Renesas/Nec Usb 3.0 Version 3.0.23.0/2.1.39.0 WHQL.
I used the 2.1.39.0 drivers -- you'll find the firmware at the same place and an explanation on how to flash the chipset we have on the P67A-GD65 (which has TWO identical chips to flash). The new firmware updater doesn't work on those, so you need to download an older firmware to use the older DOS program to flash with the newer .MEM files.

Drivers for windows xp, Dual Booting issue

I have recently purchased a mac Book pro the 13 inch model, it came with lion installed by default this means boot camp only works for 7
So ive partioned my disk using boot camp and installed Xp onto the partioned part of the hd
Obviously the issue with this is that boot camp wont let me burn a disk for the drivers as it only supports 7
so really i need someway of getting the drivers, after googling for a while i couldnt find anything so if anyone has any suggestions it would be most appreciated.
Drivers would be for such thing as the wirelsess card, sound, graphics chip etc

XP is not supported in Lion or by the newer Apple computers. There are no XP drivers for lion or for the newer hardware. This issue has been discussed repeatedly in the Boot Camp forum: https://discussions.apple.com/community/windows_software/boot_camp

Lenovo Z585 Ubuntu 13.04 / Windows 8 Dual Boot Issue - Wake from Suspend?

As the title says. I have been having an issue with waking the screen on my laptop after going into suspend from Ubuntu 13.04. (Also, same problem on Ubuntu 12.10 and Fedora 18)
When I close the lid, the computer will go into standby normally. Lights go out, and power light just blinks. Upon opening the lid I get the lights on the computer to come back and the fans come back on, however the screen stays black.
I have the following:
Processor: AMD A10-4600M APU with Radeon HD Graphics x 4
Driver: Gallium 0.4 on AMD ARUBA
I have tried updating drivers through Ubuntu. I have tried modifying the backlight controls through editing the grub.
I have tried several re-installs of multiple versions of the listed Linux above.
No matter what I do, I have the same issue(s) on all three versions.
A seperate issue is a weak wifi signal using the installed Broadcom wifi antenna. Sitting next to the router I only get about 60% strength. If I plug in my Belkin USB wireless antenna I get 100%.
Any help would be great!
Thanks

Bump

Windows 7 and boot camp issue

On an iMac a1224 I installed windows 7 then boot camp from the os disc. Bootcamp version 2.1 was installed. The current installation and set up guide suggested updating bootcamp to 3.1 however that particular update requires version 3.0. That being said, is it necessary for me to update my version 2.1?
Thanks

Leeopard huh?
You need Snow Leopard w. 10.6.x to get 3.0.
If it works and no issues fine though probably the first time I have read someone did.
BC 2.2 was more about XP and some support for Vista.

HT202008 I am having issues with my Window 7 on boot camp. My hardware is Macbook Pro Mid 2010 model and working on OS X 10.9.5. Recently I went to windows 7 to do a system upgrade but failed and was told to update the bootcamp drivers.

I am having issues with my Window 7 on boot camp. My hardware is Macbook Pro Mid 2010 model and working on OS X 10.9.5. Recently I went to windows 7 to do a system upgrade but failed and was told to update the bootcamp drivers. I installed boot camp5 but seem to be the wrong version and change to boot camp 4 which was updated okay. However I still cannot do the updates. Can someone advice me please? Thank you!

Please see Boot Camp: System requirements for Microsoft Windows operating systems - Apple Support for the appropriate version of drivers related to the specific version of Windows 7.
MacBook Pro
(13-inch, Mid 2010)
4
4
DVD
DVD
DVD
MacBook Pro
(15-inch, Mid 2010)
5
5
4
DVD
DVD
DVD
MacBook Pro
(17-inch, Mid 2010)
5
5
4
DVD
DVD
DVD
Be careful with Windows Updates, especially driver updates. Standard WHQL drivers can cause problems.

Windows 7 in boot camp - two finger click and drag issues

Hey everyone. I have Windows 7 on Boot Camp (MacBook Pro mid-2010, Mac OS X Lion) and I cannot seem to click on a window with one finger, then use a second finger to drag it. Every time I try it brings up the right click menu. Is there any way of fixing this? I want to be able to drag, darn it! Thanks.
Grant

Having had the same issue on my MacBook Pro with Boot Camp 5.0.5033 on Windows 8, workaround being external mouse, I have found the following:
If Trackpad->Two Fingers->Secondary Click is enabled in Control Panel/Boot Camp, in order to Click and Drag one cannot click any place on the trackpad. One must click bottom area of the trackpad with one finger, and then use another finger to drag.
If Trackpad->Two Fingers->Secondary Click is disabled, Click and Drag works the same way as in Mac OS X: one can click any place on MacBook Pro built-in trackpad with one finger, and then use another finger to drag the window or select a fragment of text. The two fingers Secondary Click, consequently, becomes disabled.
For me Mac OS X-style Click&Drag is more important, so I disabled two fingers Secondary Click, and assigned Bottom-Right-Corner of the trackpad to be Right-Click instead.
Don’t know if the question is still open… Hope, however, the info might be helpful to those having the same inconvenience with Click and Drag under Boot Camp.
HTH

Having issues with installing Windows XP on Boot Camp

I installed the latest firmware for my MBP along with Boot Camp. I then tried to install a copy of Windows XP that I got from my friend (we'll name him Mr.Limewire). Anyways, I've tried to use 2 different copies of Windows XP and Boot Camp does not detect the cd still (it keeps saying to insert the Win xp cd). I believe I have using the full version of Windows XP. If a copy of XP is burnt on a Mac would that affect anything?

You really need to use a legitimate XP installation CD - a downloaded copy isn't worth the time for many reasons. Even if you did get it running, you can't register it and will have to reinstall a valid copy all over again to use it.
Also read the BootCamp FAQ's - XP must be a service pack 2 (SP2) release. If you don't see a folder "SP2" on the CD or some reference to it then you likely have a pre-SP2 release.
Another option is to slipstream SP2 and create an updated XP installation CD -
http://www.winsupersite.com/showcase/windowsxpsp2slipstream.asp
but even this would be waste of time without a valid XP install disc.

Time Capsule issue with backing up Windows partition via Boot Camp

I just bought the macbook pro and time capsule. I set up a 25GB Windows partition using Boot Camp and I have set up a Time Capsule to handle the backups. Time Capsule seems to backup the OSX hard drive partition fine, with the historical versions of the drive displayed correctly. However, with the Windows partition the Time Capsule appears to be backing up any files that change, however there is no version control showing up in Time Machine. In other words, I ONLY see the Windows partitioned drive as backed up in the "Today (Now)" screen. Any historical dates the drive shows up shaded and I cannot access it. Is there a way for Time Machine to manage the Windows partition in the same way as it does for MAC OSX drives?
John

Why is it so hard?
1000 and 1 times: the drive must have FREE contiguous unfragmented space and some files are blocking and preventing.
Some are able to find and delete, some by booting from another hard drive or OS X DVD to repair and/or run iDefrag.
Or.... backup; erase; and restore.
ie, CLONE your hard drive in both directions. My choice would be SuperDuper or Carbon Copy Cloner. They tend to work. Defrag tends to be slow and if there is no backup and there is an error.... well, you'll find out.
Apple error message is badly and poorly worded. Said so for over 3 yrs and it has not changed or improved though.
Paragon CampTune 9.5 $19 is great for Boot Camp. And resizing. And Windows 7 may need 2 or 3x what the base minimums listed. 32-48GB at least to be safe. And those are conservative numbers.

SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

Hello All,
What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File with Windows, D:\ Data drive with BCDBoot).
MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
TechNet VHD Native Boot on Windows 8.1:
http://technet.microsoft.com/en-us/library/hh825689.aspx
http://technet.microsoft.com/en-us/library/hh825691.aspx
The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
which works for US before we upgrade to Windows 10 with utilizing MDT.
I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
I reported getting the diskpart script working first here:
https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
Here it is:
rem work around any USB disk left in or any CDROM detected by PE as drive D
select volume D
assign letter=F noerr
rem select the formatted volume and reassign it's drive letter
select volume C
assign letter=D
rem create and setup VHD file
create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
select vdisk file=D:\DEV_WIN81.VHD
attach vdisk
create partition primary
active
format FS=NTFS quick label="Developer Win81 VHD"
assign letter=C
rescan
exit
(type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
The Task Sequence looks like this:
I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
Question:
Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
get any issues.
I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
<![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
<![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
<![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
<![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
<![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
<![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
- and fail with an error if you have added a VHD Native Boot volume.
This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
fact what was the C:\ after Format HDD step is now the D:\ .
A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

The Mac HD has booting issues - how do I make a clone that is free of these?

I spilled water on my MacBook Air (10.6.8) and now it has booting issues.
When I shut it down, the power button doesn't work to boot it. But when I close the lid, it powers up. However even when I shut it down AND close the lid, it keeps booting up and staying on.
So I have to send it for repairs.
I cloned the Mac HD using Carbon Copy Cloner and put the clone using Migration Assistant onto the new machine (MacBook Pro - 10.7.2). Now the MacBook Pro won't boot at all. Before this, it was working fine.
So I want to know how to make a clone of the Mac HD of the MacBook Air that won't have booting issues when I migrate the clone to another machine.
I have to make a clone of the MacBook Air before I send it off for repairs as the last back up is quite old and out of date.
Also the fact that the Mac HD of the MBA has booting issues affects the ability to access the Boot Camp (Windows 7 partition) as now I can't even boot the new machine. (But I am asking about Boot Camp in another section.)
It seems like a catch-22 situation. I can't fix the booting problem until I send it off to the repair center to get the computer fixed. And yet the booting problem is preventing me from making a usable clone of the Mac HD.
I think the booting problem is a software problem because the MacBook Pro was working perfectly before I migrated the Mac HD of the MBA onto it, The MBP is only two days old. I migrated another Mac HD backup (one I made before the booting issues came up) onto the MBP on the first day I bought it and the MBP worked fine.
Do you think I will just have to clone things separately manually? I mean should I format an external hard drive, plug it in the USB port, and transfer the files I need to save? What files/folders should I save? Can I move folders or do I have to move files? I have many files in Desktop, Downloads, Documents. I also want to save my applications. I want to save the BookMarks of Opera, Firefox.
Will this take a long time? I have used about 200 GB of the MBA's hard drive.
Any advice? Thanks.
I don't use Time Machine and am not confident about using it. Will it be substantially different to CCC in the way it clones files? Will a Time Machine clone after migration contaminate the second computer with booting issues?
I am not so worried about the booting issues on the second computer. I know it's from the faulty clone and nothing to do with the machine itself. I can take it to Apple Genius Bar and they will probably be able to reinstall a new operating system on the machine and I can start from scratch, I think. I am more worried about how to save and restore my data from the old machine. Thanks for any advice.

applecore_eater wrote:
I cloned the Mac HD using Carbon Copy Cloner and put the clone using Migration Assistant onto the new machine (MacBook Pro - 10.7.2). Now the MacBook Pro won't boot at all. Before this, it was working fine.
Ok, you used Migraine Assistant to try to transfer the account from the clone drive to the MBP and it didn't work, that's ok, it can be fixed by command r booting into Lion Recovery and simply erasing and reinstalling Lion from Apple's servers. (AppleID)
I suggest you transfer the account data manually because the clone is a copy of a failing drive/corruption, use the same name in System Preferences >Accounts, drag and drop files transfer and hold option key, click on Purchases in crapStore to redownload to the new machine, install other programs from fresh sources. Cleaner machine that way. So that shoudl fix the MBP.
in the future, try to avoid Apple's "answers" like Migraine Assistant as much as possible, it's really not reliable in any sense in actuality.
So I want to know how to make a clone of the Mac HD of the MacBook Air that won't have booting issues when I migrate the clone to another machine.
You can't boot a clone of OS X from another type Mac on another type Mac, only the same exact machine model.
In your case the Migraine Assistant didn't work, so you'll have to manually install.
Also the fact that the Mac HD of the MBA has booting issues affects the ability to access the Boot Camp (Windows 7 partition) as now I can't even boot the new machine. (But I am asking about Boot Camp in another section.)
Well it's possible that Windows or something messed up the GUID partition map of the Mac, why it has booting issues. Likely why Migraine Assistant didn't work.
You'll have to set up BootCamp again on the new MBP machine, talk to Microsoft about validation on the new machine and return your Windows files, programs from fresh sources.
Likely you got malware and it was trying to write to the boot sector of the Mac, mistaking the MBR portion of the GPT for a full Windows one. This also happens when Mac users try to install Linux on their Mac's.
Unless you need full hardware performance, you really should look at virtualization software like VMFusion, Parallels Desktop or even VirtuaBox (might be outdated) and run Windows in a window on OS X instead. Much easier to recover from malware that way.
It seems like a catch-22 situation. I can't fix the booting problem until I send it off to the repair center to get the computer fixed. And yet the booting problem is preventing me from making a usable clone of the Mac HD.
Well if you make a clone, it's going to be junk any.
What you need to do is fix the new MBP machine first then use Firewire Target Disk Mode (firewire 800/400 cable and adpater if needed) and grab a copy of your files off the sick Mac or off the sick clone.
The drive is likely fine, it's just not booting and that could mean some sort of malware/drive/data corruption.
You'll have to install third party software on the new fixed MacBook Pro to read the NTFS drive format of the Windows 7 bootcamp parittion when the sick MacAir is in Firewire Target Disk Mode.
http://www.paragon-software.com/home/ntfs-mac/
https://support.apple.com/kb/HT1661

Boot issues

When I boot my computer (MacBook Pro, 15", Early 2010, 4GB RAM, 320GB HD, 2.4GHz Intel Core i5), it does nothing for quite awhile, and eventually gives me the folder with the question mark on it, signifying it can't find a startup volume. I think I know why, but this has not helped me fix the problem.
I used Disk Utility to partition the internal hard drive so I could install Linux (Ubuntu 10.10) and dual-boot. I used Linux to reformat the partition and used one of the 134MB spaces between partitions (the one at the end of the drive) as Swap space for Linux. I installed Ubuntu, and it worked fine. I could use the built in boot manager (holing down the option key at startup) to boot into either operating system.
That was last night. This afternoon, I booted up the computer, and it gave me the flashing question mark folder and wouldn't boot. I connected it to my iMac (20", Early 2009, 2GB RAM, 320GB HD, 2.66 GHz Intel Core 2 Duo) via a FireWire 800 cable and started the laptop up in Target Disk Mode. I started my iMac up holding down the option key to get it to look for the (possibly) bootable hard drive of the laptop. It did not find it, but displayed only the boot volumes normally available to it (Mac OS X 10.6.7, Windows 7 Ultimate, Mac OS X 10.5.8). I then shut down the laptop and proceeded to start it back up. Miraculously, it booted of its own accord into Mac OS X (10.6.7). I later booted the machine into Linux and began dinking around with some settings to get the illuminated keyboard to work. I did not entirely succeed, but the laptop was still working fine. I shut the clamshell to put it to sleep (while in Linux), and about an hour later, upon opening the clamshell, all I got was a black screen and the mouse pointer (as if it was stuck trying to get me to enter a password to unlock the screen). On rare occasions, this happens to me under Mac OS X as well, and I have usually been able to resolve it by shutting and opening the clamshell. After waiting a few minutes, I tried this, and when it failed, I decided to force shut down the machine, as I have had to do sometimes when this has happened under Mac OS X. Upon restarting the computer, I got the flashing question mark once again. I tried holding down the option key on startup, but only got a mouse pointer against a blank grey screen (like the boot loader screen, but without any icons). I tried zapping the PRAM, starting up in Safe Mode, starting in Verbose mode, holding down the x key, then Command-Option-O-F (then realized that wouldn't work since Apple doesn't use Open Firmware anymore), and also tried Command-Option-V-R, but that also appeared to do nothing. I just got the question mark folder each time (except for resetting the PRAM: that worked, but then I got the question mark folder).
I repeated the same steps as before (Target Disk Mode, etc) to see if they would miraculously fix the problem a second time (I still don't know how they did the first time), but to no avail. I fully booted my iMac with the laptop connected as a FireWire disk to attempt to use Disk Utility on it. Disk Utility did not recognize the drive. I checked System Profiler. It recognized that there was a Target Disk device attached to my iMac, but it did not list any hard drives under it. I proceeded to boot my laptop from its install DVD, which worked. However, Disk Utility on the pseudo-OS that is on the install DVD failed to recognize the internal hard drive. I checked under the Serial-ATA section of System Profiler. It showed two connections, one for the DVD drive, and I presume the other for the hard drive, but the hard drive one showed nothing connected to it. It simply listed a few specs on the SATA port.
I decided to boot my laptop from my iMac's internal drive. I reversed the roles of the machines, my iMac now being in Target Disk Mode, and the laptop trying to boot from its hard drive. I held down the option key at startup so I could choose what to boot from. I choose Mac OS X 10.6.7, and the machine started to boot. Just before it should have gotten to the brief blue screen before the login screen, it had a kernel panic, and the grey came down the screen and told me to restart the computer. I did, tried again, got the same kernel panic, so I decided to try Windows 7. When I selected Windows from the boot manager, it seemed to try to start up in Mac OS X (10.6.7, because 10.5.8 wasn't connected), but never got past the grey Apple icon. After a while, it started occasionally flashing a circle with a line through it, and sometimes the question mark folder, but always switched back to the Apple icon quickly. After at least 10 minutes, I decided to shut down the computer. I then tried booting Mac OS X 10.6.7 in Safe Mode. After showing the progress bar (it only got about half completed before it vanished, but it took a long time to get halfway) for awhile, it eventually successfully booted to the login screen. I signed in, and opened Disk Utility. Nothing. I checked System Profiler and got the same result I had from the install DVD. I shut down the computer, and tried to boot it normally one last time. Nothing.
Does anyone have a clue what's going on? I can understand why the computer would be having boot issues, with my shaky installation of Linux, and all, but I can't understand why nothing will recognize that the computer's internal hard drive exists.
I do have AppleCare for the laptop, unless I've voided the warranty by installing Linux. Should I send the computer in? (I'm over 250 miles from the nearest Apple Store). Is there anything I could do by opening up the computer (I know that would void the warranty if I haven't already). I do have a backup of most of the data, but the backup excludes some video files because of their size. Luckily, I do still have them on MiniDV tape if I have to reimport them.
I feel like I've tried everything, but I wouldn't be surprised if I've missed something obvious…
Thanks in advance for any ideas, suggestions or answers!

Update 2: That successful boot seems to have been one of about four flukes. For some strange reason, my computer will successfully boot into Mac OS X and Ubuntu, but only on rare occasions. There seems to be no pattern, but every once in a while, the computer will decide to recognize it has a hard drive.
Any thoughts?

Windows not finding Boot Camp on MacBook Pro

Hey everyone. I have Windows 7 64-bit and a MacBook Pro (mid 2010) with OS X Lion installed. When I boot up in Windows, it seems that only half of the time Windows realizes that it is on a Mac. Meaning...only half of the time the Boot Camp program is running in the notification tray, and only half of the time will Windows register the volume up/down, brightness up/down, and keyboard backlight up/down buttons on the Mac. It makes it very difficult to say...adjust the brightness or volume in the middle of a game. I can still go out of the game and turn up the volume in the notification area, but it is becoming a huge hassle. Like I said, this is only happening about half of the time. The other half of the time Windows registers that Boot Camp is on it, there is the Boot Camp icon in the bottom right corner of Windows, and all of my control buttons (brightness, volume, etc.) work just fine. Any ideas on how to make this happen every time? Thanks.

Hello Bhagyeshree
Check out the articles below to troubleshoot issues with connecting to Wi-Fi. Start with creating a new Network Location and then search for a Wi-Fi network and if that does not work, then go through second article to troubleshoot the issue further.
OS X Mavericks: Add a network location
http://support.apple.com/kb/PH13788
Wi-Fi: How to troubleshoot Wi-Fi connectivity
http://support.apple.com/kb/HT4628
Regards,
-Norm G.

Booting issue on a new installation on Acer Aspire 4752 laptop.

Hi All,
     I have done a new installation of OS on a Acer laptop stated above. However, due to some reason, during the booting up process, it will always stuck at screen right before it enter into the logon screen. I will have to press
Enter in order to move it, as if there is a "press Enter to continue...".
     After this "enter" key, everything else works normally. However, this is pretty annoying and I could not sent this laptop back to my enduser because of this trivial issue.
     Some other information as below:
This is a new OS and no other apps is installed. Though now it is patched (with Microsoft patches). But it happens since the first boot after install.
In according to Device Manager, all drivers are in place. No exclamation mark and error.
Event Viewer shows no error for the boot up.
Safemode (command prompt) shows that it is stuck at loading "classpnp.sys".
     My questions:
It will be good if there is already a resolution. :)
How to diagnose, or identify which apps actually waiting for that "enter" to move on?
     Thanks!
wsn

Hi,
For the boot issue, first I suggest you use startup repair if you have an installation disk, check if it can detect and fix some certain problems.
Or run sfc/scannow in command prompt in recovery console, check if it can make any difference.
If doesn’t work, then try “Enable boot logging”, then check the log called ntbtlog.txt, usually located in system drive\Windows.
Advanced startup options (including safe mode)
http://windows.microsoft.com/en-in/windows/advanced-startup-options-including-safe-mode#1TC=windows-7
You can also share a screen image with us about the “stuck” screen.
Regards
Yolanda
TechNet Community Support

Windows 8.1 Boot Issues

Similar Messages

Maybe you are looking for