GrofLuigi
Content Type
Profiles
Forums
Events
Posts posted by GrofLuigi
-
-
On Win7, I see Version : 3.1, not LFS Version, which is not present in the output of fsutil fsinfo ntfsinfo C: . Maybe Win7 doesn't expect new LFS versions? AFAIR this "bug" also affected Win7, or in other words, it started with Win8 and every disk formatted by a lower OS version than 8 is affected by any higher OS version.
The registry value NtfsDisableLfsUpgrade fixed it for me, so much so that I almost forgot about it. It is always one of the first things I apply to any new installation >8, before it has a chance to see a <8 drive, and never had any problems.
GL
0 -
See this (It's about Win8, but Win10 is the same). Especially the last paragraph(s). I think when Win10 saw that disk(s), it autoconverted them to higher NTFS version (regardless of the possible incompatibilities of early NTFS versions mentioned in this thread).
I had the same situation before (but involving XP and Win8/10) and chkdsk /f solved it. But it had to be XP's chkdsk.
GL
0 -
Is your date/time correct? Too much drift can cause certificate verification errors.
0 -
It turned out I don't need it, thank you.
0 -
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?
0 -
%Localappdata%\Microsoft\Event Viewer\ ?
(That's on Win7, it might be the same on 10.)
GL
3 -
Try AUOptions=dword:1 in the same key.
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).
0 -
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.
Just a wild guess.
GL
0 -
Erm... Press NumLock?
2 -
I guess that's Administrative shares. Still goes through SMB or "shared folders".
GL
0 -
I didn't understand much of it, but if it is true (and especially after it's developed further) it looks very bad...
We discovered serious weaknesses in WPA2, a protocol that secures all modern protected Wi-Fi networks. An attacker within range of a victim can exploit these weaknesses using key reinstallation attacks (KRACKs). Concretely, attackers can use this novel attack technique to read information that was previously assumed to be safely encrypted. This can be abused to steal sensitive information such as credit card numbers, passwords, chat messages, emails, photos, and so on. The attack works against all modern protected Wi-Fi networks. Depending on the network configuration, it is also possible to inject and manipulate data. For example, an attacker might be able to inject ransomware or other malware into websites.
The weaknesses are in the Wi-Fi standard itself, and not in individual products or implementations. Therefore, any correct implementation of WPA2 is likely affected. To prevent the attack, users must update affected products as soon as security updates become available. Note that if your device supports Wi-Fi, it is most likely affected. During our initial research, we discovered ourselves that Android, Linux, Apple, Windows, OpenBSD, MediaTek, Linksys, and others, are all affected by some variant of the attacks. For more information about specific products, consult the database of CERT/CC, or contact your vendor.
The research behind the attack will be presented at the Computer and Communications Security (CCS) conference, and at the Black Hat Europe conference. Our detailed research paper can already be downloaded.
0 -
0
-
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.
0 -
They type it faster without having to worry about when to press SHIFT, so they save few miliseconds.That's RAPID enough.
0 -
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
0 -
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
0 -
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
0 -
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
0 -
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.
0 -
It seems, data about your music and photos. Maybe also holds data for other UNIversal STORE apps (DataBase).
0 -
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
0 -
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
0 -
Task scheduler?
(I don't know enough about it to give a proper example.)
0 -
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:
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
0
) or
Can connecting a Win-NT4 drive as a slave to a Win-10 system mess it up?
in Windows 2000/2003/NT4
Posted
NTFS Version.
GL