New
#11
Thank you for your help. That runs cleanly, I would never have worked that command line out!
Unforunately, even after a reboot I still get the same error with Windows update. :-(
Thank you for your help. That runs cleanly, I would never have worked that command line out!
Unforunately, even after a reboot I still get the same error with Windows update. :-(
Too bad that didn't work
Try a clean startup:
Launch System Configuratiion (msconfig)
on the Services tab:Press the [Disable all] button
on the Startup tab:Press Open Task Manager
Disable all items listed
Close Task Manager
Press [Ok] on the System Configuration window
Restart your machine
Try a manual Windows Update from Settings -> Update and Recovery (not Control Panel)
The issue might be HW related.
A few other suggested fixes were to run wsreset
This might have more affect (works on Win10, not just Win8.x)
Store - Re-register in Windows 8 and 8.1
Try all three and test an update.
I have not had much luck! There is another new version of W10 due out later this month so I will try and upgrade to that.
When I upgraded to Build 9926 annoyingly a 450mb partition was created on my SSD without my consent. Fortunately the area used probably was really blank rather than containing a hidden partition. I consider it a rediculously dangerous thing for MS to have started doing.
I have just tried making this partition visible to W10. Doing this has not solved my problem.
Ok, I would go with a clean install from the ISO when you do the install with the next build.
IT's not clear if you upgraded your base system (Win10 over Win8.x) or if you're dual booting or using virtualization. I haven't read your thread again, so maybe the information is back a few posts, if not - please describe the way you're installing Win10 ... it helps. There might be a different approach (I tried bare metal install, Boot-to-DVD, Hyper-V virtualization, and a regular dual boot).
Bill
.
I use a boot manager BOOTIT Bare metal to manage various OS on my SSD. Each copy of Windows has its own partition. Only one partition is visible at a time. The remainder are hidden.
I did a fresh clean install of W10 preview from a USB stick two builds ago.
The first build upgrade worked fine, the second upgrade to 9926 appeared to work OK though it did create the recovery partition, and Windows Update no longer works.
Thanks.
I did a fresh clean install of W10 preview from a USB stick two builds ago
The first build upgrade worked fine
Make it easier for me, what were the build numbers?
Probably moot since you said you were going to wait ... but I strongly recommend a clean install when the next build drops.
Win10 is Preview release code - you're install isn't working as it is now. No sense battling alpha code issues unless you really want to. I think this sort of issue really falls into the MS arena.
I still don't see any system information for your machine. Hard to troubleshoot when you're blind on this side.
450 MB partition? Odd - usually it's 100 or 350 MG depending on BIOS or UEFI - is your machine UEFI? I don't know how BootIt takes UEFI into consideration.
When I upgraded to Build 9926 annoyingly a 450mb partition was created on my SSD without my consent.
How would you have answered the prompt if one was offered?
This is one of the good features of Windows - it figures out the disk schema.
I guess this thread can sit idle unitl the next drop - another member might drop in and offer suggestions.
Good luck,
Bill
.
Thanks for your help.
I could not remember the build numbers! My PC is quite old it uses an Intel E6600 processor - no UEFI
I like to allocate disk space (partitions) myself, particularly necessary as I have hidden partitions that might get overwritten.
I have no need for a recovery partition as I keep image backups.
Fair enough, my memory isn't all that great either
I'm not certain that Win8 or Win10 will function without the Recovery partition - it's part of the way Windows works after Win7. I suppose it can be done, but is it worth the effort?
I'm pretty sure that if the space is partitioned, then Windows won't touch it (other than boot code sectors). I could be wrong, though - so experimentation on your part with hidden partitions is probably a good idea (I don't see the need, but understand everyone operates their machine the way they see fit).
Windows has become quite smart as far as install and updates go. I'm curious to know if the hidden parts were affected or if Windows figured it out and did the right thing (right as far as Windows is concerned, it's apparent that you disagree with the Windows schema).
What's the advantage of BOOTIT over the Windows manager/loader? I have Vista / Win10 on one machine (separate parts - dual boot) - and Win8 /Win10 (VHD, dual boot) on another. I don't have any non-Windows (Linux) booting from the HDD, but I do boot Mint separately from a thumb drive.
I guess you're still waiting for the next build to drop and you plan on a fresh install using the ISO - is that still the plan?
Bill
.
I have had BOOTIT for a long time and I know how it works. One thing I can do is make clone copies and use those for testing etc.
Windows manager/loader is no doubt much better than it was.
Perhaps by luck I don't think the recovery partition did destroy anything else. It was placed after the "W10 C:" drive on my SSD. Had it gone in the 'Unallocated' area before my "W10 C:" drive it would have clobbered a hidden partition.
Will the next build use the same recovery partition?
Win10 will create the Recovery partition in every build, as far as I know.
Um... how can unallocated space be a hidden partition? Perhaps it's just terminology, but unallocated space is well, not allocated. If you're using some form of encryption and hiding partitions, then that's out of my experience.
What wizardry do you employ
Post a screen shot of your disk management from the perspective of each of the OSes - that might help me see what you see.
Disk Management: Custom console to post screen shots on the forums.
How to create a Disk Management screen shot using custom consoles
Check your Start to see if you already have the custom Disk Management consoles downloaded.
There are two custom consoles included in the download for this tutorial:
- dmDskmgr-vg.msc - presents Volumes in the top pane and Graphical view in the bottom pane
- dmDskmgr-vd.msc - presents Volumes in the top pane and Disks in the bottom pane
and two corresponding shortcuts are created in your Start
- dmDskmgrVG
- dmDskmgrVD
If you already have these shortcuts in your Start, you do not have to download them again.
Just launch the tools(s) and grab a windowed screen shot (Alt+PrtScn, paste (Ctrl+V) into Paint and save),
then post the screen shot on your thread.
See: https://www.tenforums.com/tutorials/1...en-forums.html
If you do NOT already have the tools, follow these steps to download and place the tools in your Start
- Download dmTools.zip
Select [Save] on the download action bar
-> The default save location is normally your Downloads folder (i.e. C:\Users\Dad\Downloads)
!! Warning !! The batch file included in the zip folder depends on the Downloads location and it will fail if you save the zip file to a different location.
- When the download completes, select [Open folder] on the download action bar
dmTools.zip should be selected / highlighted
Press the Extract menu
Select Extract all
Accept the pre-filled defaults on the extract dialog window
An Explorer window should open showing the extracted folder dmTools
You can close both Explorer windows, the compressed folder and the extracted folder, at any time.
- Launch a standard Command Prompt
Navigate to the folder you just created when you extracted the file from the zip folder
(i.e. C:\Users\Dad\Downloads\dmTools)
Run the dmToolsMk batch file to make the required folders, copy the required files and create shortcuts on your Start.
Enter the following commands in Command prompt:cd %UserProfile%\Downloads\dmTools
dmToolsMk
exit- Test the tools in your Start. There should be a dmTools folder with two customized Disk Management consoles
Start -> All programs -> dmTools -> dmDskmgrVG
Start -> All programs -> dmTools -> dmDskmgrVD
For most machines, the console presentation will not require any adjustment.
If however, your machine has many volumes or many disks, you might have to adjust the panes.
-> Drag the middle separator up or down as required.
To get the most information in one screen shot, you might also have to maximize the window to include all of your disks / volumes.
When you have the screen shot ready to post, see: https://www.tenforums.com/tutorials/1...en-forums.html
That's about it.