glnz

SD73 - Eleven? I'm envious. What is the 11th?

Ten updates (including for Office 2003-7). So, who's going first? (Not me - water's too cold.)

Sherylinrm and jaclaz - unfortunately, the XP machine with the Seagate HD-SSD glitched again yesterday - it froze. (Did not see whether it was also a BSOD - probably not because BlueScreenView doesn't show anything from yesterday.) I think you're right about the Hard Drive. Too bad, as the machine's original Western Digital Velociraptor HD was nice (10,000 RPM). Since this HD is a hybrid HD-SSD, will cloning software like Aomei Backupper or Macrium Reflect have any difficulty "reading" everything on the drive and then "restoring" to a normal (NON-hybrid) HD? By the way, when I first "backed up" from the Velociraptor and "restored" into this Seagate a year ago using Aomei, I needed to recreate its bootability using my Macrium CD - it wasn't booting. But that went well. One last question - do you think it might be TeamViewer causing my HD to freeze? Is it possible that the latest versions of TV don't like XP?

EDITED - FOUND REPORTS For the second time this past week, an Avast Boot-Time scan has some odd error messages but its "Scan History" says there were NO bad files. See my post on the Avast forum at https://forum.avast.com/index.php?topic=192475.0 . (<-- You might have to try the link twice to get to my thread.) Any thought whether the error messages are linked to the freezes the last two months and my two BSODs? (The Boot-Time scan meant I rebooted, but still no new BSODs or freezes last 48 hours.)

drugwash - Ran memtest and also the Diagnostics boot option in my Dell (selected after F12). All good - no errors with my CPU or RAM. Thanks for suggestion.

Dave-H - Thanks for the link to Nirsoft's bluescreenview. It let me see that there WAS a cause to the latest BSOD - namely mbam.sys with a STOP 0x00000019. Yes, it was running in the tray (and I have since UNchecked it as a startup item, so it's not running now). Should I upload here anything from bluescreenview? Does it reveal confidential info? Drugwash - I might try AFT later. By the way, so far almost 24 hours no BSOD and no freeze when I try to access using Teamviewer (which I'm doing now). Thanks.

OK - OK - I get it! Jeez - talk about touchy! The first of my two recent BSODs blamed aswsp.sys with a STOP 0x00000050. That's an Avast file for its own software protection. The second BSOD yesterday didn't blame any file at all, and I did not shoot a photo of it. (I remember a lovely shade of blue and a lot of white letters that reminded me of clouds or soft, fluffy cotton.) There was nothing useful in Event Viewer. I suppose I could look for a minidump file and maybe attach it here? (What's its exact file name, and where is it likely to be in XP?) On one of my recent reboots the last 48 hours after starting to fiddle with msconfig, I saw that Avast was off, so I Repaired it. I set msconfig to full "Normal" after that, and that's how it's been going since. No BSODs since. Yes, a bunch of .sys lines in the ntbtlog are from third party software I've installed over the last 30 years. From your posts here, sounds like those .sys entries aren't so important. One service I shut off the last 24 hours after going to full Normal on msconfig was related to Aomei Backupper - its automatic scheduler, which I never set and never used. So, even with all the .sys lines, after I'm completely booted up and have a coffee, I have 2.6± GB showing as available RAM (from 4GB installed), which is pretty good. Well, let's see whether I get any more BSODs or freezes. I forgot to say at the beginning -- Before I got these two BSODs, my PC has been freezing about once per day the past month or so, requiring a manual reboot. Again, nothing interesting in Event Viewer. (I frequently access this PC from my work office using TeamViewer - to check on private emails at home. The past month or so, about once per day, this PC has shown in the TV list but then won't connect and then drops off the list.) Well, now that I'm using Normal in msconfig, let's see if that continues as well. Cheers!

I'm a bit ... concerned. My trusty old XP machine is giving me some BSODs. I started a new thread on this forum at xp-growing-hair-need-a-barber-how-to-cut-back-msconfig-load-everything . Could it be some of the recent updates? Thanks.

I'm a BIG fan of this forum's top-notch thread on the POS hack for keeping XP updated through the 24th century. But, just the last week, my trusty old Dell Optiplex 755 XP machine (4GB RAM) is getting CRANKY. A few BSODs. Various sweeps by Avast and MalwareBytes and last August's MRT don't show anything. So I ran sfc /scannow, but I saw in Event Viewer that it couldn't check or replace a whole bunch of files. So I re-ran sfc /scannow after setting msconfig to diagnostic mode. Twice. Then, when I returned msconfig to its typical combination of Selective Startup - Process SYSTEM.INI files + Process WIN.INI files + Use Original BOOT.INI, I had more problems. So I am now rebooting with msconfig set to "Normal Startup - load all device drivers and services and run the dishwasher." After a few reboots, I am really getting bored. But I also ran a Boot Log reboot, and its list of drivers loaded is much longer than I remember. Here it is (or look nearby - I uploaded it). glnz's latest XP reboot ntbtlog 10-27-16.txt What do you think? What drivers (.SYS files) should I turn off, and how do I do that anyway? PLEASE NOTE that my list of Services has stayed fairly slim. The numerous services that I changed to Disable or Manual over the years have stayed that way. (Thanks again to trusty old CodeStuff Starter.) This is not a Services issue, as far as I can tell. However, I'm a real estate lawyer, not a techy, so what do I know? NOTE - Since last year, my hard drive has been a Seagate Momentus XT hybrid HD-SSD that we bought for a different computer in 2013 ±. I think it's getting a bit skittish, and it might be a source of the BSODs. However, it passes the Seagate SeaTools for Windows tests. The Momentus XT is model no. ST95005620AS (500GB). What do you think about my ntbtlog.txt file?

I'll try! I promise!

Gents - on my XP machine (kept updated with the POS hack thanks to dencorso and friends), will the transition to ESR happen automatically, or will I have to do something? Also, I don't know what ESR means (Extra Special Rubberband?), but the important question is: will it continue to get security updates from Mozilla? Thanks. PS Ever since FF dropped "Ask Me Every Time" for cookies, I don't like them so much anymore. Like how I feel about Delta Airlines. But I love NoScript, BetterPrivacy and Disconnect, so I'm still there.

Installed the seven and (manually) the two .NET updates listed above. However, now, Microsoft Update is prompting me to install "Security Update for Microsoft .NET Framework 3.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2756918)" as an Important update. Is that one OK, or is this a glitch? Thanks.

Ok, everyone - I see seven in my list. But I admit it - I'm a coward. Has anyone been braver than I?

Frank - when do the pubs close? 10pm? Let's ask MS to stop GMT at 9:30. Cheers to Novosibirsk!

Novosibirsk ?? Do people in Novosibirsk even care what time it is? It's either 24 hours sunlight or 24 hours darkness, but always vodka time. Uber is a reindeer.

Trip - I am assuming that very few people have this problem, so who knows maybe it WAS tested by MS. Or very few people first installed O365 32-bit by mistake and then uninstalled and reinstalled with 64-bit. Or nobody checks their Event Viewer. Problem is - the MS tech 2 who is "helping" me insists it's my OS and he wants me to repair my Win 7 Pro 64-bit OS by doing an "inplace upgrade". But my sfc /scannows are 100% pristine clean. I just want help with these "cannot change protected registry key" Warnings in Event Viewer.

Attached is an evtx file of the 70 or so Warnings in Event Viewer. This evtx file will open in your Event Viewer. Any ideas? Thanks. 70 Warnings of protected registry keys.evtx

Alas, my "scrub" idea above didn't work any better than anything else, and again on UN and REinstall of O365 I have 70+ Warnings that protected registry keys could not be modified. The MS tech person sees some .dll errors in netdll.dll and KernelBase.dll and so is recommending I do a non-destructive repair of my Win 7 Pro 64-bit via an "inplace upgrade" off a Win 7 Pro 64-bit iso. Comment? Thanks.

jaclaz - many thanks. Two Qs: 1) I think I saw on this forum guidance about downloading a "technical" copy of the Win 7 Pro 64-bit .iso and pointing to it when doing a scannow or some other file-repairing cmd command. Do you recall that, or can you give me the link? I remember it only worked with the right "technical" and not "other-typical" download. (Or am I confusing this with Win 10?) 2) The SHA1 code matches, but how do I check the MD5? Thanks.

I've been bugging MS to help me with a problem doing a 100% clean Reinstall of Office 365 Home 64-bit on my Win 7 Pro 64-bit PC. Each Reinstall of O365 creates 70± Warning messages in Event Viewer that certain registry keys are protected and cannot be modified by Office 365 Click-to-Run. (O365 actually works fine so far - I just don't like those Warning messages and want to Reinstall without them.) The MS O365 help line tech 2 level person accessed my PC and showed me how my further Event Viewer error messages show errors with ntdll.dll and kernelbase.dll. He says the only way we can fix the problem with Reinstall of Office 365 Home 64-bit is to repair those dll's in my Win 7 Pro 64-bit OS, and the only way to do that in a non-destructive fashion is to do an "inplace upgrade" of my Win 7 off the .iso image of Win 7 Pro 64-bit. What do you think? First, please see the very interesting article about non-destructive repair using inplace upgrade at http://mcs-notes1.open.ac.uk:8080/tbtknowl.nsf/0e36766f24334c4c80256554005a57dc/8779f10d83d5276e8025794400355753?OpenDocument (I have also attached that article to this post.) Second, following the instructions of the MS tech 2, I am downloading an .iso of Win 7 Pro 64-bit from http://91.121.154.109/Windows 7/Eng/ . Do you like that source? The .iso I am downloading is called en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso. I see that the file's date is August of 2015 (last year), so that means I'll have to do a lot of Windows Updates afterwards (and carefully so as to avoid the updates that install the Win 10 "spy" features)? Do you think there are better .iso sources for the install, maybe already updated? The Third, he also showed me the normal MS Windows .iso download page https://www.microsoft.com/en-in/software-download/windows7 , but when I inserted my perfectly good Key for my Win 7 at the bottom of that page, it did NOT verify. He said that MS's verification server is down, and has been down for some days. (Really?) I know my key is good because I used it for a re-install of the OS almost two years ago on this PC. Fourth, my PC is actually dual-boot Win 7 Pro SP1 64-bit and Win 10 Pro 64-bit. (FYI - I have separate keys/licenses for each - the 10 is NOT an upgrade of the 7.) Do you think the non-destructive repair of Win 7 using inplace upgrade will wipe out the 10? I think I'm OK because I did a destructive 7 repair about 1½ years ago, and that did not wipe out the other OS (which was then 8.1, since changed to 10). But is there anything special I should do to preserve the 10? Fifth - reminder that my core problem isn't with the OS, which seems to be 100% fine. It's only that I am getting 70+ Warning messages about non-modifiable registry keys whenever I reinstall my O365 Home 64-bit. Hey, what do you think???? Easy, huh? Thanks. Win 7 non-destructive reinstall instructions.htm

5eraph, Bersaglio and FranceBB - Many thanks. All installed. Belarc Advisor says so. But what shall we do about the end of mrt.exe? Isn't that another chink in our old, dented, squeaking armor? Stuxnet, here we come (keeping our dishwasher on the Extra Rinse cycle forever)! FranceBB -- may I call you Frank? -- are you an Avast person? If so, many thanks for good free product. Please keep it XP-usable.

Also, I ran the eight updates, but my PC glitched on the first run-through, and I am now unable to get KB3184122. It shows in results only with a question mark, and it doesn't come up again if I run MS Update again. The others eventually all installed with green checkmarks (although I had to stop Avast AV to finish KB3185319). How can I get KB3184122 manually? Thanks.

There's no new Malicious Software Removal Tool (mrt.exe)? It's not in my list of eight updates.

Bersaglio - I saw an update to Silverlight in the MS Updates list just now. Same as yours? I see eight updates, including three for my old Office. Anyone have any issues with these?

To readers - I have a clue how to a fix this problem with non-modificable registry keys, but need your suggestions. I am now looking for "Scrub" that will truly UNinstall Office and O365 from my PC, including the registry keys that cannot be modified during the REinstall process. A MS tech suggested this "Scrub" but only if he runs it on my machine - not something he'll send me. Do you know what he means by "Scrub"? Do you believe what he tells me, that it will actually delete those 60 - 70 non-modifiable registry keys? Where can I get this on my own (or at least research it before he wrecks my PC and kills two of my work days)? After the call with the tech, I found something on the web about "Offscrub", and it might be helpful. It also might be very helpful when you are UNinstalling Office from many PCs. Go to the following great article and then please come back here to comment: https://www.deploymentmadscientist.com/2016/02/08/deploying-microsoft-office-2016-removing-old-versions/ After you read the above, here are my questions: If I open cmd as administrator, what would be the single command line (from that article) to run either O15CTRRemove.diagcab (easier for me) or offscrub?.vbs (more work for me) in the strongest flavor? (I assume I would first have to create the CScriptNative.cmd described in that article.) I am hoping this approach will delete those 60 - 70 registry keys as well, so I can then do a REinstall without the Warnings. (By the way, before I got to the article above, an MS office tech called me this morning. His first recommendation was to Repair or Reset my operating system, Win 7 Pro 64-bit. Instead of telling him what I thought about that (and him), I bit my tongue and asked him (a) whether he'd read my txt files with copies of the Event Viewer Warnings and (b) whether an OS Repair or Reset would focus on those keys. I continued to ask questions, and he eventually mentioned "Scrub" as the answer, which later inspired me to the link above. Anyway, I asked him to call me back in two weeks when I would have time to do this, and he promised to do so. I don't trust this guy's knowledge, and I would prefer to find a more reliable solution.) Thanks, and I hope you all find this link helpful in your work.