Replies

I ran the Crucial diags on it when it first failed and it was okay. I quick formatted it like you’re supposed to and then cloned my hard drive to the SSD w/o issue. What I did see however was the recovery partition on the SSD was huge. On my 1 TB drive it’s the standard 450MB. On the SSD 40% of the 512MB drive was recovery partition…like 180GB, yeah GB not MB. The conclusion that the drive may be ill, might be correct. On the bottom of the EaseToDo back up there’s the note that Win10 AU requires sector by sector backup. I didn’t allow the update installation because I never did install AU. I don’t know why the huge recovery partition. Space was not an issue on the SSD even with the humongous recovery partition because I’ve only got 134GB of stuff on my hard drive, so why did the cloning process create that huge of recovery partition…..Anyhow, with all the issues and the painful morning, I’m back up and running with my trusty, dusty WD Black and I’ve mothballed the Crucial SSD.

Diane

No, I can’t. I tried it several weeks ago and we just replaced the cables from “C” into the SSD, and booted up. The results were even worse than what I got yesterday. I had no keyboard, no mouse and never got past the desktop. We’re going to give it a go again. I think I read somewhere where others have had success just running it as IDE. In that we will be in the PC anyway, might as well give it a shot as IDE and just change the type of drive to solid state and make sure the boot priority was correct. BTW, the system disk was never on Channel 0, ever. We looked this AM. There’s nothing there. It’s location must have not been a problem all this time.

I don’t understand any of this however, because I first used the SSD when my PC was first built as the primary drive; “it called itself AHCI” and it ran flawlessly until I corrupted the thing going from Win8 to Win8.1. I lost patience with it after spending hours trying to get the PC to run and just took it out and thought I salvaged it….Later

D.

Addendum…to finish the saga. We gave one last try to get the solid state drive to work properly incl changing the BIOS setup/AHCI. The thing still crashed my system altho’ it did bootup quite nicely and quickly; when we changed AHCI, I got inaccessible hard drive error. Better than this though, when we moved the WD from its old channel to the 0 channel, I almost fainted when I got the inaccessible hard drive error for my “C” drive; then we couldn’t get into the BIOS because the keyboard stopped working and we didn’t know it. After we figured out that, I still had the inaccessible hard drive error and couldn’t get into the BIOS; then I got into Safe Mode, elevated command prompt and we took a shot at chkdsk and that worked so I’m back up and running with “C” as “0” and “D” as disk 1, but it certainly was a rough road getting there.

I just looked in the BIOS and it turns out that the “C” drive shows up on Channel 5 and Channel 0 has nothing detected. What will happen if I moved the drive around from 5 to 0 in the BIOS. I looked in my manual and I see where channel 0 is. I just don’t know if that’s where the drive was originally connected. I’ll have to have my husband open the PC again and look on the motherboard.

I presume that’s where we decided to put it, not knowing any better. 🙂 If I like what I see, then I’ll move it around in the BIOS and see what happens. Thanks again

D.

Thanks for your response.

I never did install W10 AU and I’ve installed all the Windows updates so far that have been offered w/o problems. I don’t do the hardware on this system, so I’m embarrassed to say, I’m not sure what channel my System/Windows drive is connected to. It is the Intel chipset. I’m certain of that. Do I actually have to fix the drive order if it’s working? I’m just afraid if I start juggling drives around on the motherboard I’m going to screw it up big time.

The PC is homebuilt, so I don’t really know how the drives ended up in what connection, to tell the truth. It’s been this way since it was built and this is the first time I noticed the drive numbers were botched up.

Diane

I ask because I’ve been following other posters here and issues that have arisen. I also have been faithfully following Woody’s site and the issues about updates and there really hasn’t been any big blowups there since August about AU 10.

I don’t feel the particular need for AU but did want to keep myself informed in the event it’s offered or I decide it’s time. I’d hate to mess with a PC that isn’t broken. Thanks to you both for your replies.

Diane

As I read the note at the bottom of the screen at EaseUS, it said the sector by sector backup is a requirement for Windows 10 AU, which I don’t have yet. Anyhow, I did check the Optimize for SSD Box. Hopefully, the migration will go okay.

As always I appreciate the help.

D.

The sector by sector explanation makes sense to me. To take this one step further, that must mean that there will very little difference then between clone and system image backup?

Thanks very much for the help with drive letters.

D.

I just find interruption of reading email by dimming my screen and telling me an update is required massively intrusive and not necessary although I’m sure MSoft is worrying about me more than they have to.

I absolutely think you’re right about more spying. At least when I went to the windows update screen they didn’t push the download button on my behalf.

Diane

Just an FYI…I’m reading mail in Thunderbird this morning; my screen gets darker and I get a popup….”Windows Updates are required. Download updates.” I have no choice bit to click on the button to get the download because there’s no other way to get rid of the screen.

I’m taken to the Windows update screen and it shows KB3150513, but I still have to click on the button to download the KB. I’m not liking this behavior much. I’d bet this popup is going to appear every time I bootup and maybe more times during the day. It made me feel guilty. 🙁

Here’s part of the introduction in the KB article:

“This update provides the latest set of definitions for compatibility diagnostics that are performed on the system. The updated definitions will help enable Microsoft and its partners to ensure compatibility for all customers who want to install the latest Windows operating system. Installing this update also makes sure that the latest Windows operating system version is correctly offered through Windows Update, based on compatibility results. ”

Based on that I’d install the fix. I’d rather have some assurance that the AU will be compatible.

Do you think the fix will force the AU even tho’ it might still be causing issues? I just don’t yet have the confidence in “compatibility diagnostics”

D.

I read the article you posted. Doesn’t tell us much does it.

I am no expert, by any cyberstretch of the imagination, but doesn’t the vague language make you wonder whether or not checking up is being done to see if AU has been installed? I have flicked my off switches and quite frankly am going to hate the thought of losing that ability after AU. I thought I read that the ability to use the Group Policy Editor in Pro will go away after AU. All I can say is go EFF.

Diane

I asked @ Woody’s…..his note and some replies; nobody seems to know much about the update. Not inclined to be made an example of, thank you very much.

https://www.askwoody.com

Sorry for my written shorthand. I edited my system using the Group Policy Editor…GPE’d is so much easier to say 🙂 so updates aren’t force fed

My system is not Win 8.1, but Win10 which has me wondering why I got it at all and what makes me leery

Diane

I couldn’t tell from your post if you or your friend tried WSUS. Do give it a try.

We found a couple of updates after WSUS ran; they installed; the one failure was the Malicious Software removal tool. I didn’t much acre about that update because you get a new one every time Windows updates, that is if you can get them at all. I told Bob to hide it; he re-ran it anyway and it installed; after that exercise we checked for updates and it did so quickly. We’ll hang on to the ISO DVD image WSUS made in case we have further probs with the old laptop, but do give WSUS a try.

You will need a couple of free hours depending on how fast you can get the updates on your system. WSUS has saved us twice now on the same laptop, once after a clean install of Win7 and the other–the labor intensive task of just trying to get updates to work.

Thanks for the info with regard to AutoPatcher.

I just spent 3 days trying to fix WU on a laptop that can’t handle an OS above 7 because to do so would disable HDMI ports and not allow for updating Nvidia drivers. I tried every remedy known to man. We ended up after all the fixes with 6 important and 4 optionals from June 20th. The only thing that fixed it was WSUS Offline. After completing the run of WSUS, we were able to check for updates, download and install them perfectly fine. But, I understand from reading that this fix may not be permanent and updates/patches may malfunction again.

My question is this…does Autopatcher fix connectivity problems like WSUS does or at least did for us? I couldn’t seem to tell from your post whether or not it does. In our case we couldn’t get updates dated later than June, couldn’t install them and couldn’t get new ones. Fortunately this laptop is only a backup system and not used regularly. I just get so agitated with M$oft. Not everyone has a system that will run Win10 or wants it.