• PeachesP

    PeachesP

    @peachesp

    Viewing 15 replies - 31 through 45 (of 186 total)
    Author
    Replies
    • in reply to: Photos/Outlook.com #2289753

      Thanks so much for your response…makes sense.

      D.

    • in reply to: Desktop v. Microsoft Account for Win10 v1909 #2268258

      Not quite because I never did sign-in to Microsoft account until yesterday and didn’t realize what my desktop would look like.

      If it is considered a duplicate post, I apologize for breaking the rules.

    • in reply to: Desktop v. Microsoft Account for Win10 v1909 #2268252

      It was my M$oft account desktop that was a mess. I understand it is two different accounts, but I don’t recall the desktop changing its appearance in the past. You used to be able to just sign-in with either your local or Microsoft account and the both were the same.

      The old behavior must have changed sometime ago because I don’t recall signing in with different account and the desktop being different. That goes to show you how often I connect with the company that watches over me. 😉

    • in reply to: How to repair CBS log errors #2070033

      The solution to my issue is a follows in case someone might care about this topic or find it helpful…

      Version 4.8.1908 update for Windows Defender is required. All of the following DISMN commands need to be run:

      DISM /Online /Cleanup-Image /CheckHealth

      DISM /Online /Cleanup-Image /ScanHealth

      DISM /Online /Cleanup-Image /RestoreHealth

      When I ran sfc /scannow the results were no longer corrupted so that sfc /scannow could now again be relied upon as it was in the past

      1 user thanked author for this post.
    • in reply to: How to repair CBS log errors #2010523

      Thanks for your info. Unfortunately, after running chkdsk, Dism and scannow, I still have the same corrupted files.

      However. your suggestion prompted me to do some further research because I never used the DISM command before. I found that the errors I have are not unusual and have something to do with the version of Wdefender on the PC, that I tried to update in Windows Security, but there was no update to be found. The site suggested three DISM commands be run..checkhealth, scanhealth and restorehealth. I did that,  followed up with scannow and I still have the issue with the corrupted defender files. I am beginning to conclude that the flaky computer doesn’t give a rat’s behind that I have file integrity violations when I run sfc /scannow. I also am starting to conclude there might be hardware issues lurking in the background. I just don’t know what they are just yet.

      D.

    • in reply to: Having an Awful Time with Windows 10 Mail/Outlook #1591901

      Thanks for your response.

      What I really wanted to do, was to just eliminate the Microsoft Mail account and just use the local one. I don’t want to sync anything, just have a secondary trouble-free account without Microsoft checking up on me all the time to see if I’m doing okay,, but not botch up my PC in the process. :p

      I’ll do some poking around to see what I can come up with before I create a restore point and do some experimentation.

      Diane

    • in reply to: Outlook Mail Profile #1587902

      Thanks to B & C for helping.

    • in reply to: Outlook Mail Profile #1587891

      The issue went away “voluntarily” after two days…the address I am using is https://outlook.live.com/owa. I’m not sure what the “owa” is. I will try the ping test next time I have issues, but I haven’t had a problem since. I don’t know if my use of Chrome to simply create a shortcut to the desktop could possibly be the cause, but it was the easiest way to get the icon on the desktop with just a click or two. Neither Opera my default browser or FFox offers a simple solution to creating a desktop icon for outlook mail that I could find. Anyhow, all is well.

      Thank you both.

    • in reply to: Gave Up on SSD #1587820

      Got it. Thanks.

    • in reply to: Gave Up on SSD #1587817

      I’ll tell the end result of my troubles with my Crucial MX100. I took it out of my PC and stuck it in my MacBook Pro “training laptop”. The OS erased and formatted it, found it and its fully functional. The drive apparently is okay.

      I bought a Samsung 850EVO. Had to initialize it and create a simple volume for my PC to see it; ran their Data Migration software that cloned the drive successfully and didn’t mess with partition size like EaseUS software did with the Crucial(it used 1/3 of the drive and I couldn’t resize them for some reason).

      Disconnected the HDD and installed the SSD; changed UEFI from IDE to AHCI and the drive did not work properly. Got BSOD telling me there was a problem with my PC. It was installed on Sata 0. So, knowing now that the problem was with my PC and two SSD’s neither of which were probably faulty, I did the “regedit” thing as recommended by the poster below to who I am very grateful.

      I don’t know if this is helpful, but there are posts in the Windows 10 forum: “AHCI – Enable in Windows 8 and Windows 10 after installation. This is the link: http://www.tenforums.com/tutorials/?. ACHI has to be enabled in the bios and in Win 10. The instructions tell you how to enable ACHI in Windows 10 after installing it in IDE mode.

      This was the whole issue to start with. Why I didn’t have a problem with Windows 7 when I first used the Crucial is not known to me, but Win 10 requires the regedit fix. Of the 4 places where DWord had to be fixed, only two of mine were messed up, but after applying the changes, my SSD is fully functional. The manuals that Samsung provides are somewhat lacking. The install guide is just pictures. The cloning software is used that came with the drive was different than what was in the manual. The Samsung Magician software that installs first is the software you use after the drive is working, but not much is explained very well. Not a word anywhere about WIN10 and no native AHCI drivers. Anyhow, I am pleased with the new drive and happy as a clam that we were able to figure out what the problem was with the help of the OP.

    • in reply to: Outlook Mail Profile #1587467

      I do need some further assistance now.

      I moved my stuff from my secondary email account @ Yahoo because of their issues and created the account at Outlook and have been using it a few days now and it serves its purpose for news reading and other unimportant internet stuff. I’m using it with my Chrome browser simply because I was able to create a desktop icon w/o major problems. I used it this morning, reading a few things. And now, I can’t access my account with the following message:
      “outlook.live.com’s server DNS address could not be found.” I checked to see if the problem is just mine and apparently it is.

      I’ve read some of the solutions at Microsoft tech site and they are recommending fooling around with changing the DNS to a google public DNS.

      Can someone help me with this? I’m afraid I’m a total dork when it comes to network issues, DNS’s and things. Is there a fix that I can understand how to do? I did delete the cookies and rebooted the PC a couple of times.I also tried to access outlook with other browsers with the same results. Perhaps I should just look around for a secondary mail service that doesn’t give me such hassles. I already have a gmail account for semi important stuff, but I need another for non-important surfing, newsletters, etc

      Thanks for any help

    • in reply to: Outlook Mail Profile #1586916

      Thank you so much. Appreciate the help.

    • in reply to: Windows 10 Update Disabler #1585857

      I thought from the reading, that it would allow you to pick and choose what you wanted. No, it isn’t advisable, of course to stop updating.

      D.

    • in reply to: Gave Up on SSD #1583636

      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

    • in reply to: Gave Up on SSD #1583616

      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.

    Viewing 15 replies - 31 through 45 (of 186 total)