Nomen

I tried the following, on a win-7 system and also a win-10 system that were both showing this behavior: internet properties / security tab / local intranet / sites - uncheck "automatically detect intranet network" local intranet / custom level / miscellaneous section - drag and drop or copy and paste files (enable) - launching programs and unsafe files (enable) The above did not change anything. I then found this: https://www.thewindowsclub.com/these-files-cant-be-opened-in-windows Which had the following reg edits (done from an administrative command prompt): reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Associations" /v "DefaultFileTypeRisk" /t REG_DWORD /d "1808" /f reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Attachments" /v "SaveZoneInformation" /t REG_DWORD /d "1" /f And that DID fix the issue. On both systems. A reboot was not required. It's really confusing why right-clicking on a zip file on a network share comes back with a security message warning of "opening" the file. I'm not trying to open the file when I right-click on it to bring up the context options. Why is that such a big security issue? (on both systems, I think that winrar was the default handler for zip files, would that make a difference here?)

I've got a Win-7 computer that can access shared folders on other PC's on the local lan. If I navigate to a shared folder and view files, then right-click on pretty much any file I get the usual context menu (copy, cut, properties, etc). But if I right-click on a zip file, a Windows Security box opens, with a message saying - Opening these files might be harmful to your computer - Your internet security settings blocked one or more files from being opened And I'm pretty much stopped from doing anything with the files I've selected or high-lighted. If I open the "internet properties" window, I can set the properties for - Internet - local intranet - trusted sites - restricted sites, I assumed I am dealing with the local intranet. Its security setting was set to medium low. I changed it to Low. This did not change anything. There are times when want to highlight and copy collections of files from a shared network folder, but if the selection includes a single .zip file, I'm stopped dead in my tracks when I want to right-click and select Copy. Instead I get the stupid security warning. How do I change this behavior of windows blocking the context menu from coming up when I highlight a single file or group of files on a network share that includes zip files?

What is that 3.1 version then? Version - of what?

There are times when you might want to attach hard drives from say win-2k / xp / 7 systems to a win-10 box to perform some sort of operation (like bulk file copy or diagnostic or malware scan or clone) but win-10 will mess up these attached drives and render them un-bootable when returned to their original hardware. There is mention of a registry key (NtfsDisableLfsUpgrade) for use in Windows 8 that is supposed to prevent that, I was wondering if it works in Win-10, and I'm also wondering if there's a utility or method built into win-10, or perhaps third-party software, that can undo this LFS "upgrade" to restore an older NTFS volume to its original state.

Does this exchange here from 2015: https://answers.microsoft.com/en-us/insider/forum/all/windows-10-649860-windows-7-617601-dirty-flag/1520f41d-eb80-490b-b8be-7acd9d53c031?page=1 mirror what I'm seeing? Except it deals with Win-10 corrupting win-7 volumes?

--------------------- Type “fsutil fsinfo ntfsinfo <the drive letter of your volume”; example: fsutil fsinfo ntfsinfo C: You should see output similar to the below. -If you see the entry “LFS Version” as 2.0, than your volume has been upgraded to the high performance Logfile structure only compatible with Windows 8. -If you see the entry “LFS Version” as 1.1, than your volume is using a Logfile structure compatible with previous versions of Windows. ---------------------- I'm running Win-7 Ultimate SP1 32-bit and I'm seeing version 3.1 when I run that fsutil command. Last I checked, 3.1 is numerically higher than 2.0, while 7 is less than 8. Curious. Regarding the registry value NtfsDisableLfsUpgrade, for one thing I don't see it on this Windows 7 PC I'm using to type this, but if creating that entry and setting it to 1 means don't upgrade mounted NTFS from 1 to 2 then what does it mean when the OS drive is already at 3.1? Will that result in an immediate downgrade of the running hard drive? Or does it mean don't change the version when mounting any NTFS volume? ------------- Close the Registry Editor and perform a system Restart (not Shutdown) to downgrade all mounted NTFS volumes to a log file structure and version number compatible with prior versions of Windows. Upon the next boot of Windows 8, NTFS will no longer upgrade the log file structure and version number to 2.0 if the above key was set to a non-zero value. -------------- That seems unworkable. You want your existing OS drive to maintain what-ever NTFS version level it currently has, AND you don't want any new mounted NTFS drive to be messed with. Is there a registry entry (for win-10) for that?

The 2 NT4 servers I have running are both SP6. Their initial creation was circa 1998 probably, and through cloning over time have migrated to larger drives. A few months ago I had used Ghost 3 (?) on floppy to clone one of them from an 80 gb drive to a 128 gb sata SSD, worked fine, booted fine, etc. Today I took a number of old backup drives and tried them in a couple different motherboards while booting an actual original NT 4 server installation CD. Upon booting I selected r (for recovery or repair) and every time I'm told that no NT4 installation can be found. The repair thing also asks if you have an emergency recovery disk (which I never made). All of these old backup drives can actually boot NT4. They were 6, 40 and 80 gb size drives, all IDE. The motherboards were circa 1998 to 2000, P2 or P3 (in a socket card). When the NT4 CD boots up, it loads a bunch of drivers, then at one point it detects mass storage devices and it does detect the ATAPI / CD / IDE interface and on one board it detected the SCSI (yes SCSI, not sata) hardware interface that was on this board (it was a Gigabyte BX440 board). For all drives except the 6 GB drive it threw up a warning/message screen about drives with more than 1000 cylinders (I think it was cylinders) as possibly being an incompatible geometry. For a while today I was thinking I needed to give the NT cd a floppy with an appropriate IDE storage driver on it when it asks for additional drivers, and I looked through a lot of different motherboard driver CD's I have that are dated 1996 - 2004 and I looked on the web and I can find NO hint that there is such an animal. The boot partition or volume on the 6 gb drive I had was 2 gb, so no possibility there of incompatible size. So why the NT4 installation CD totally rejects these drives as having working installations of NT4, who knows. It is likely that at one point or many points in the past these drives were connected to XP boxes to have defragging and virus scanning done to them. The 80 gb drive that started this problem has 2 partitions or volumes, both NTFS, the first is 12 gb, the second is the rest of the drive (64 gb I think). But it doesn't matter, if the installation CD can't find an NT4 installation on 2 gb partition on a 6 gb drive then wtf. I also tried the Repair option from a bootable XP-SP3 CD - this time XP does see the NT installation but it asks for the admin password, which I know what it is and I gave it, but XP said wrong password. Go figure. I'm going to get this box up and running from an old(er) backup drive and then copy the current files that were in use from this pooched drive over. Has anyone ever had any luck restoring boot-ability to an old NT drive using utilities like Kaspersky, Hirens, etc?

Yea there's a lot of good info there, primarily if you are setting up a new NT4 install from scratch, and some info about connecting newer version OS drives to NT4 and NTFS tool compatibility. But nothing really about what happens when an NT4 NTFS drive is attached to a newer running system (XP, 7, 10, etc) - something you might want to do for file transfer, file system checking / repair, backup or cloning reasons. This incident happened yesterday, I'll be back at it today at some point.

If I connected this drive to another running NT4 (or win-2k) system, what commands or utility can I run that might restore the boot-ability of the drive? I also read about some sort of 7.8 gb volume or partition size quirk that might or will mess up NT4's bootability if some files get moved beyond that point on the boot volume. ?

I've sort of known that if you connect an NTFS drive as a slave to another system running a more recent NTFS version (say, connecting an NT4 drive to a Win-XP system) that "things happen to it" such that you might not be able to run the NT4's native drive-fixing tools (scandisk or defrag) any more. But I've never NOT been able to put said drive back into its original box and it fails to boot. So here's the situation: I've used Ghost booted from a floppy many times to clone NT4 and XP drives (usually 80 gb IDE drives) to make backup copies of them. I have a couple of NT4 boxes that are for mail and web servers. I've decided it's time to clone the NT4 web server. So I whip out the Ghost floppy, do the clone, but Ghost says there's a problem (I think a logical problem, not a bad sector). I try different Ghost startup options, but can't get past this. I have Macrium reflect installed on a win-10 PC, I've used it to clone itself to another drive and I'm surprised but yes it works, and the clone boots. Ok, so I connect the NT4 drive (80 gb) to the win-10 PC and I connect a blank SATA drive (128 gb) also and have a look at Windows Disk Manager and I can see them so everything looks ok there. I fire up Macrium, select the source and destination, select sector-by-sector, and start the clone. Half an hour later, it's done. I put the clone drive in the NT4 box and try to boot it up. This is what I get: Disk I/O Error: Status = 00000001 NTDETECT V4.0 Checking hardware ... Disk I/O Error: Status = 00000001 NTDETECT failed Great. WTF. Ok, I take the clone drive out, plug the original drive back in, and GET THE SAME F ing message. Why did just pluging my NT4 drive into the Win-10 box to clone it f it up? Could it be something as simple as Win-10 set a flag on the NT4 drive to disable it's boot status? IE - make it non-bootable? Is there a rule that says any NT-based OS can't stand having more than 1 bootable drive/partition on a system and if it sees it it takes action? Or has something deeper happened to the NT4 drive that's going to require major surgery to correct? The NT4 drive has 2 logical partitions or volumes (C drive and D drive). When I have the cloned NT4 drive in the win-10 box, I can see all the files on the "D" drive, but it tells me I (or "it") doesn't have permission to see the C drive files. So I "took ownership" of the C drive and a few minutes later after all the file-scrolling was done I had access to the C drive and all the files are there, root directory, etc, so all the files are there. Is there any drive utility I can put on a bootable floppy and fix the original drive, or make the clone boot on the original box? Or do I have to drag out the original NT4 CD and start putzing with this?

This is a long shot, but... I'm trying to prevent my win-2k domain server from making Krazy-a** dns requests such as: _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.(my_domain) _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.(server_name) _ldap._tcp.dc._msdcs.(my_domain) _ldap._tcp.gc._msdcs.(server_name) I don't know where "Default-First-Site-Name" comes from but I might have seen it in the registry somewhere. There might have been a couple more, I put them in the HOSTS file and I plan on putting the above in there tomorrow, but I'm wondering how I can stop the machine from trying to perform DNS queries on those things. I've pointed this 2K server at my router as the DNS server and I'm logging these requests so that's how I know what they are. The DNS sub-system on this 2K server is really messed up but it doesn't matter, the machine does what it's supposed to do, it's hosting an exchange server and the PC's that need it can connect to it. I just want it to stop making these Krazy DNS queries.

A few days ago I installed "Simple DNS Plus" on a win-7 PC that is not always running. I had changed the third DNS server setting on the Win-NT4 server PC (the subject of the thread) to the LAN IP address of this win-7 PC. Trying to capture the DNS request being made every 8 hours. I was lucky today - here's what the Simple DNS logs captured: 11:12:24 Listening for DNS requests via UDP/TCP at 127.0.0.1 port 53 11:12:24 Listening for DNS requests via UDP/TCP at 192.168.2.137 port 53 11:12:24 Listening for DNS requests via UDP/TCP at ::1 port 53 11:25:26 Request from 192.168.2.130 for A-record for 192.168.2.1 11:25:26 Sending reply to 192.168.2.130 about A-record for 192.168.2.1: 11:25:26 -> Answer: A-record for 192.168.2.1 = 192.168.2.1 Hmmm. The NT server (at 2.130) is making a DNS request for the host 192.168.2.1. So, 192.168.2.1 is my LAN router. It's also the gateway IP in I guess all TCP settings for all devices on the LAN, including this win-NT box. Somewhat odd that something on the NT box is making a DNS request for an IPv4 IP, and the OS is actually going through the motions and making an external DNS request, not for a host-name but for an IPv4 address. Now I don't know, in the DNS world, whether or not making a DNS request for an IP address (especially a private / un-routable IP like 192.168.x.x) is kosher, but it seems that this request is failing for both the primary and secondary DNS servers and hence it's falling to the 3'rd server (which used to be 4.2.2.2 but is now the local PC running Simple DNS). It doesn't seem legit to be doing this, presumably the OS is supposed to just return the IP address as the result and not make a fool of itself by going out to make a (bogus?) request? As to what program or service on the NT4 box is making the request, I have a no idea what it could be. I do have something called "About Time 4.8" (an NTP time checker/setter) running on the box, but it's also running on another NT4 box and both of them are using 192.168.2.1 for the NTP time server, and both are set to do an NTP time check every hour (not every 8 hours). The Post.Office SMTP software is the only other service that's running (that I know of) that has a reason to do DNS queries, but I can't associate anything in it's logs with these queries for 192.168.2.1 every 8 hours. Perhaps as a start I can put this into HOSTS file: 192.168.2.1 192.168.2.1 and see if this actually prevents the NT box from doing DNS lookups on that LAN IP. But as to why it's doing that, any clues as to how I can figure that out?

There was something called the "Creators Update" that was released in early 2018 that added an address bar to regedit so that you could directly type or paste in a registry location to jump to. I have no idea for what versions of Windows this Creator's Update was for, but I'm wondering if this update is available for win-7, or if not, if the relavent exe/dll files are available somewhere and can be dropped into a win-7 installation to enable this feature.

I've got an NT4 server system on my network that runs an SMTP server. I have my router log in-bound and out-bound traffic to/from the machine and also restrict it's access to the internet beyond a few necessary ports. So in the logs I'll see traffic on port 53 (DNS) and 25 (SMTP). The machine's TCP settings have 3 DNS IP addresses, 2 of which are my ISP's DNS servers and the third is 4.2.2.2 (a generic server that I've used for years as a DNS backup and also for pings to test for IP connectivity). I happened to be looking at the logs recently and noticed that the NT server does make port 53 DNS requests to the first DNS server IP entry when it's sending an out-bound email, but curiously, exactly every 8 hours to the second, it makes what I'm assuming is a port-53 DNS request to each of the 3 DNS servers. Does NT have a DNS checking scheme, where it just checks for DNS server connectivity on a schedule? I'm thinking of setting up a DNS server (simpledns) on a win-7 PC on the network and point the NT4's third DNS IP setting to the win-7 PC just to be able to capture this request and see what the machine is trying to lookup. Unless there's a way I can do it on the machine itself.

What about installing Win-10 on PC's with OEM keys built into the motherboard firmware? I assume they'll always activate now and in the future?

This is a laptop running windows 7 ultimate. The desktop is extended to an external monitor. In the power plan settings, when plugged in, the "put the computer to sleep" option is set to never. In advanced power settings, under power buttons and lid, the lid close action when plugged in is set to hibernate (on battery it is set to sleep, but it is always on ac power). Yet, when I close the lid, windows tranfers all open windows to the still-powered external monitor. It does not shut down or sleep or hibernate. Can anyone explain this?

I've come across comments like Powershell has to be V2 for these commands to work - how do you get the powershell version? I've also come across that in Control Pane, - Progams and Features - Turn Windows Features on or off, that SMB is supposed to show up in the list, but again I don't see it. What about enabling all versions of SMB? How is that done? I will mess with the various file-sharing settings and see what happens...

I'm looking at pages like this: https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows And I'm seeing instructions like this: Powershell: Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol And I get errors like this: get-WindowsOptionalFeature : The term 'get-WindowsOptionalFeature' is not recognized as the name of a cmdlet, function, script file, or operable program. (...) (BTW, does it matter if there is use of mixed case (uppler and lower case letters) in these commands?) I come across this thread: https://social.technet.microsoft.com/Forums/windows/en-US/35330530-0488-4ddc-8544-6f95cec51abc/getwindowsfeature-missing?forum=win10itprogeneral which is primarily about "get windowsfeature" but does mention "get windowsoptionalfeature" and it talks about the function working one day then not working the next day, and also mentioning that it might only be available on windows servers (but Windows 7 is not a server OS but these commands must have worked on win-7 at one time in the past???) Does anyone know a way to enable SMB on windows 7 and/or Windows 10? I don't care what SMB version as long as I can share a folder with an iPhone connected via wifi to the same local LAN.

I seem to recall that win-7 has some sort of validation that runs as a service, and if you disable it you will get a message on your desktop along the lines of "your copy of windows may not be genuine" or something like that. Does Win-10 have the same thing? Also, I'm very familliar with XP and how it's validation was tied to a bunch of different hardware fingerprints and you needed 5 or 6 "votes" for it to continue to think that it's a valid install otherwise it would need to re-validate itself. There was even a program (xpinfo.exe) that would tell you which hardware elements were contributing (or not) to this vote scheme. I'm not sure if Win-7 works the same way in this regard as XP does, and likewise no idea how win-10 operates in this regard. If win-10 does the same thing as XP, is there software available that will show me the validation status based on hardware fingerprint?

I don't understand the relationship between the motherboard RAM architecture or RAM sub-system and the M.2 interface. The HP computer in question has (1) NVMe 2242 and (1) NVMe 2280. The smaller one is used by the installed wifi/BT card. I assume I can install an SSD in the larger one? I read somewhere that M.2 SATA is not supported.

I'm pretty sure its a S01-pF1013w. The HP service app on it said that the 1 year HP warranty expired just a couple months ago. This thing looks brand new, not sure where these come from, maybe leased? For what it has, I think the $170 I paid for it ($125 USD) is a steal. Came with a new mouse and keyboard. 1 TB internal hard drive, 4 gb ram, 4 USB-3 ports in front (which for some reason HP doesn't refer to as USB 3 but as "SuperSpeed USB Type-A"). Yes, I see that it will be limited to 32 gb ram (2 x 16 gb) but I'm not planning to go beyond 8 gb. Just wanted to make sure Win-10 home wasn't limited to 4 gb. I see that 4 gb DDR-4 ram is somewhat hard to find (locally). Having 2 sticks of 4 gb would be faster than a single stick of 8 - yes? Dual Channel?

OK, after some searching I've found directly from M$ that the "physical" ram limits for Win-10 home is 128 gb vs 2 TB for Pro. I don't know how it's even possible to generally have more than what, 64 gb of installed ram in your "average" desktop computer. So basically there is no real distinction in terms of max installed ram when you're looking at Home vs Pro. This is a big difference compared to Win-7. M$ created more low-budget versions of Win-7. Win-7 "Starter" was limited to 2 gb and was only x86. Win-7 home basic (x64) was limited to 8 gb and Home premium (x64) was limited to 16 gb.

The point is that when you buy new or refurbished hardware, it's already going to have win-10 "installed" on it, and there won't be any media disk for you to use to "install it yourself". So the only thing you can do is to go through the motions when you take it out of the box and turn it on. It's going to ask for any info it can to identify a pre-existing microsoft account. Your only option is to give it a phone number that you've never given to M$ before. And I'll ask again, does win-10 home have any set ram limits? How exactly is win-10 home handicapped vs some other flavor of win-10?

I've picked up an HP Slim Desktop Celeron G5900 as a refurbed unit. It has 4gb and Windows-10 home 64 bit. I was wondering if there are any RAM limits for W-10 home (ie maybe it's limited to 4 gb?) otherwise I was thinking of throwing another 4 gb ram into it (I'm guessing it would help performance?). I'm somewhat new to win-10, but I see if I'm going to migrate some PC's from 7 to 10 I'm going to have to dig into this a bit. One of the things I'm not liking is when you go through the initial power-on phase of a system with pre-installed win-10 is that it wants you to have a microsoft account (instead of a local account) and there doesn't seem to be a way to bypass that. Beyond that, has anyone come up with a single "god-mode" or "power-user" package that will make all the mods that you'll eventually stumble on doing over time as you hammer and mold a stock/retail win-10 installtion into something more useful for a power user? Like taking ownership of the /etc folder so you can control the hosts file? Turning off all crap services, uninstalling all the stuff you won't use (or will refuse to use on principle) like office 360, onedrive, etc?

Roytam came up with Retrozilla - yes? I've been using that for a while now on my win-98 systems (which do not log into any websites). I usually have to set the View Style to None to make a site useful to view, but it works for what I do on those systems. Regarding chrome - I've stayed clear of chrome on any other PC I have (which are win-7) because of my "perception" (which could be wrong?) that chrome is tied in too heavily to google (in terms of backdoor, telemetry, etc). Is my perception correct? I would feel comfortable using a "chromium" based browser if it was as disconnected from Google as Firefox is (or can be) from Mozilla. Are there links to download packages / installers for the top candidates mentioned here (360 Chrome and DC Browser) or do I have to figure out how to actually get my hands on them?