GrofLuigi

Is your date/time correct? Too much drift can cause certificate verification errors.

It turned out I don't need it, thank you.

Sorry if I don't follow, I just now needed Dism tools for the first time. So this tool is dead dead? No chance to make it work? I need to download the full thing?

%Localappdata%\Microsoft\Event Viewer\ ? (That's on Win7, it might be the same on 10.) GL

Try AUOptions=dword:1 in the same key. Link I guessed it even before finding that link, that is the option to usually control updates (and Microsoft doesn't want to know about option 1 and usually omits it from descriptions).

I don't follow this topic too much, but is it possible you have hit the limit of 16 kb or 330 certificates that XP allows? I remember in the past that was an issue. Something like this. Just a wild guess. GL

Erm... Press NumLock?

I guess that's Administrative shares. Still goes through SMB or "shared folders". GL

I didn't understand much of it, but if it is true (and especially after it's developed further) it looks very bad...

So this doesn't work?

I put Win2000 because there was no option for Win2003, the most stable Windows ever. Maybe I should have put XP, but I think my way of usage is closer to 2000 (which I have also used in the distant past), although not much as a server. My work consists of, it could be said, office and Internet usage. I haven't played games (at least big ones) for a long time.

They type it faster without having to worry about when to press SHIFT, so they save few miliseconds.That's RAPID enough.

Yeah, it was the release version, I just copied the numbers from above. Double check: firefox plugin that I kept is 26.0.0.131 here. Beta version never entered my computer. GL

It is definitely Flash. Opera worked fine for years, I just regularly updated the plugin (replaced NPSWF32.dll in C:\Program Files (x86)\Opera\program\plugins\). Now, when I did that with flash 26.0.0.133, there were few days of crashes. I reverted to 25.0.0.171 and not a crash since. I can't think of a better proof that it's Flash. GL

Flash plugin V26 (NPAPI) is a crash fest on my Opera Presto (12.18) on Windows 7, I cant imagine that it would be anything else on lower OS. Just replaced the file with V25 and no problems again. Just FIY. GL

Don't know if this still works for OS>XP (please notice the reference at the bottom). Otherwise, you might try this (I know nothing about the program, can't guarantee it isn't malware ) or Nirsoft's Volumouse (not exactly logarithmic, but allows for finer control). GL

They broke into your house and listemed to your conversations; whether they used them or not is irrelevant. Now Mavroudis suggests you make a special door so they can enter your house and do whatever they want to do, so they don't listen your conversations? Nice job, Mavroudis.

It seems, data about your music and photos. Maybe also holds data for other UNIversal STORE apps (DataBase).

Usually it's hiding in UPPERFILTERS or LOWERFILTERS of other devices. Delete ASATAFLT from there. I take a strong hint from the FLT in the name (filter). Also, try searching for ASATAFLT in the registry and track down everything related to it (for example guids or other long strings - search for them; then for anything related to them and so on; taking care you don't delete something you'd need). GL

Find msinfo32.in_ in your source, expand it (I use Universal Extractor, it is also possible with command line) and you'll see what is needed. It's quite simple. I think (I'm not sure) you can right click it and install it. You'd need to provide MSINFO32.EX_ too (whether expanded or not, I don't know). It is located at the same place as MSINFO32.IN_. I don't see other files mentioned in the .inf file, but there are some with similar names (.dll). Maybe you'd need to provide them as well, or they are already present in \windows\system32 (Nlite doesn't remove them?). Another way would be to put expanded MSINFO32.EXE directly into \windows\system32 and hope for the best. Maybe try regsvr32 msinfo32.exe in the command line (and also provide the .dll if it isn't already present and try that line on it too). I'm not on XP right now, but looking at my preset I can't see it (but then, I didn't remove it there). I think it was called "System Information" or something. GL

Task scheduler? (I don't know enough about it to give a proper example.)

No, MsiInstaller is a different thing, an EventLog source. It's not an "entity" in the security sense to give it permissions. So it's case #2, broken installer that breaks the registry. In any case, I doubt you should run the installer from that location (Program Files), unless you are trying to uninstall it (which I strongly suggest you try, because I think nobody needs that). I can't do quotes in this editor properly, so I'll just try to paste, if that works: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_officeinsider-mso_other/what-is-office-16-click-to-run-extensibility/ebffe8d7-ac9c-4a88-bf1b-3d7cd402848d Things like Windows Desktop Search integration, the OneNote Printer Driver, Primary Interop Assemblies (PIAs), and Visual Studio Tools for Office (VSTO) are things no normal user should ever need. They are bloat aimed to drag you into Microsoft dependency, which would be the case if they were slightly useful, which they are not. It's another thing if Office doesn't work without them (as I read that version 15 breaks 32-bit Office if uninstalled), but there is some chance it won't break. You could (have) tested this if you tried to run your Office programs after uninstalling it, but before reinstalling it. But it's not too late to try again. Better way would be to use Add/remove programs and uninstall only the Extensibility Component, or use Nirsoft's MyUninstaller to find it among all possible entries. Otherwise, the way to fix it is to make a bug report to Microsoft or edit the .msi with Orca or similar tool, both tedious tasks. GL

I wouldn't bother if I were you, except if you have extreme case of OCD and want to satisfy it. I am prety sure everything works even now (without the "fixes"), except 0.01% of chance that ink/handwriting component won't. I give it such a small chance because the keys are still present and if needed Word (or any office program) could invoke the component (call it). What is potentially broken is some parts of them, or registry values, that couldn't possibly be so important. The registry values are part of COM registration (mostly used in inter-process communication), and because the main keys are present, I think it will still manage to call them just fine. That's if you ever use ink/handwriting. Edit: the forum editor wouldn't acknoledge ENTER, even for a single newline, so I tried some key combinations and CTRL+ENTER posted the unfinished text. Now where was I... "Will Repair... create different keys and so progress will be lost?" (I'm re-typing this because copy+paste also doesn't work) - Well, it depends. Obviously, the installer script is broken, but is it broken in such a way that it has unrealistic expectations (that the keys are unprotected) or it breaks them itself? I don't know, but if you insist on Repair Install, I think it could make no additional harm, except possibly the need of "de-protecting" them again later. I think repair install has a better chance than uninstall+reinstall, and is less work anyway.

I don't think WRP is protecting registry keys, but I am not sure. I haven't seen it in action because I usually apply many tweaks at the same time aimed to "tame down" the system, so I am not sure if any of them is preventing that. At the same time, I often go nuclear on my systems and apply blanket full permissions to myself (or Administrators group, to be exact) and SYSTEM to whole branches of registry. Sometimes it bites me back and some (many) things break, so I don't recommend you do that. What I think you should do is this: > Should I ALSO give "Administrators" Full Control permission? YES. I think that might help you, if you don't mind editing 60+ permissions. And I returned and read this topic from the start, and now I think you shouldn't bother much about this, ink/ink divider/ink whatever is office component for tablet mode / handwriting recognition, not important at all. I suspect most other keys with errors are related to it too, the CLSID and INTERFACE registration of the "ink" components. "Ink" has steadily progressed through Microsoft OSes to be more and more important (for them). It wasn't present in XP, only installed with Office 2003, then it became system component with many CLSIDs and other registration components in 7 (or maybe Vista, I'm not sure) and increasing its presence in later OSes. I suspect Office 365 is expecting (being programmed to expect) Win8.1 or Win10, where "Ink" is even more prominent and is not prepared for what it sees on Win7. Just a wild guess. Whatever the reason, I am almost sure you wil not encounter any problems even if "ink" is not working, and additionally I'm pretty sure "Ink" will still work even with these errors anyway. GL

That TIdo.cmd is as powerful as it gets. I've done all kinds of mischief with it. The output of Whoami is not what it seems to be. It either lies (not accounting for the rights of the parent group, which apply to the current user), or the disabled/enabled state is not what we think it is: https://social.technet.microsoft.com/Forums/windowsserver/en-US/e24a35b3-fb72-4918-8e51-562e2ad8d8f5/what-is-the-state-column-returned-by-whoami-priv?forum=winserversecurity And, as far as I know (at least until previous versions of Office) OSSP doesn't protect anything else besides Microsoft's profit, in the sense that it bans you from running unlicenced versions of Office, but doesn't actively protect any resources, including registry keys. I repeat, AFAIK. GL