Tripredacus

It sounds like your company needs to re-evaluate their internals. At any manufacturing company, computers that run critical machines should either be segregated or firewalled. Or the company should be using a WSUS and only push updates to it that have been vetted beforehand. Alternatively, they may be using the wrong (but cost effective) SKUs. I see that a lot where a company will save costs by using a retail OS instead of an Embedded/IoT OS. Last year I got to visit a company and do a site inventory for them. Their critical machines controlled lasers for micro-manufacturing, and none of the computers attached to those systems were connected to the internet. For the same reason you outlined, because if one goes down, manufacturing stops and the company looses big dollars. So they had made it so those systems did not get updates. That company also were using the "wrong" OS for the job as a reason to cut costs (I don't want to think about how much those laser machines cost) and that was their mitigation strategy.

Your first post was moved to the Startisback forum. Your second duplicate post was deleted. Do not make duplicate posts in the forum, it will just annoy the users and give everyone a bad impression.

Finding exact info is kind of tricky but I know this. Almost a year ago is when the big stations switched to ATSC 3 in my area. When that happened, the CBS and NBC affiliated stations can only be picked up by the ATSC 3 tuner I bought for my upstairs TV. My downstairs TV can't get those channels anymore and they are not found when doing a rescan. Maybe I have my numbers off, maybe that TV only has ATSC 1 and those stations changed to 2 and not 3.

The issue seen here is that since the rearm was used, it put the licensing system into grace period. So this means that the initial cause for Windows to be in notification is not know because Windows does not log previous states as far as I'm aware. There may be something in Event Viewer indicating when the licensing change occurred. These are kept in a combination of Winlogon and Security-SPP sources at a logon. Security-SPP will initialise the status check and will log the status, afterwards Winlogon will write an even which normally would say "Windows license validated." As far as the status log by Security-SPP, this log is also written when MGADiag is run and potentially there would be a way to compare a log where the OS is in notification, in grace period and in activated state. However, since the system is in grace period, we can't know for sure why now it is in Notification. By looking at the log files I can confirm a legitimate OS is installed but obviously I can't confirm the partial. The OS does appear to be System Builder. There is not present any file corruption that interferes with licensing. Now what to do. First make sure the time is set properly in the BIOS and then verify the time is correct in Windows. Verify that the partial product key in the logs matches the one on the COA. Attempt slmgr -ato again. If it says the product key is blocked still, then there is only one thing left. You run slui 4 and call the number. But one thing to keep in mind when dealing with a person at the Activation Center, you don't need to explain anything and the less you say the better. You can say that your Windows is telling you to activate but it doesn't. You can say you have the COA and the product key and ask for help to activate. There is no need to say anything else, nothing about the computer itself, no small talk, nothing about what you have tried to solve the issue already. The Activation Center has the keys to the kingdom and what you say will determine whether they run the code generator for you. If, when you call into the phone number, it gives you the option to text you a link instead of talking to someone, do that. Because that link will have the activation code generator (you put in your product key and it spits out some numbers that you type into Windows to activate). In my experience, this code generator will work 99% of the time presuming that your key isn't flagged as "stolen" on the Activation Server. If the rep still can't help and/or the code generator rejects your key then the option to buy another key is an option... BUT it should be a key for the same SKU aka Windows 7 Pro SP1 OEM System Builder. With a new key, you can try to use slmgr /ipk to change to the new key and slmgr /ato to activate online, but you still may need to use slui 4 to call the activation number with a new key.

I collected videos for about 10 years, so I still have years worth of VHS and DVD to watch before getting rid of it. That includes many DVD box sets for TV shows that I binge watch. No real difference really, except that I've missed out on anything recent.

Name changed.

Is that a captcha message?

Those with pets know about daylight savings, or the fact that their animals who expect them to be home or fed at a certain time get weird until they adjust to the fact that you decided to leave/come home from work and feed them at a different time for some reason all of a sudden.

I can't make use of an edited output. If you are wary about sharing the full output of the two tools, you can PM me the full information. EDIT: since you used rearm (should not have been done) now you are in grace period. You can run the slmgr /ato as suggested above, and if you get an error, relay that error here.

I never got one of those boxes at the time either. As back then there was a satellite TV setup at my house, but I had gotten rid of it sometime in 2011 or 2012. At that point in time, I did end up getting a digital converter box that I had used sparingly, but I found without having a million channels at my disposal, I ended up not watching very much. Now it is only to watch sports that are on broadcast TV. I have still resisted having purchased any streaming subscriptions, but there are enough DVDs I can watch if I want to become a couch potato.

Those converter boxes are worthless now in many areas, including my own. As they were from the 2010s they do not support ATSC 3.0 which some operators have changed to. Even my primary HD TV cannot get most channels anymore because of this change so you have to buy a new OTA receiver (or new TV I suppose) to be able to receive them.

I suspect that this type of reasoning is made up by people who aren't or haven't any farming experience. I did work (and live) on a farm for some time and I can say that it makes no different if there is DST or not. You work from sunrise to sunset (or beyond but indoors) and you determine what time to wake up based on what time the sunrise is the next day.

Send to me the output of slmgr -dlv as well as run the MGADiag program and use the copy button to output the data to a text file and send that along also. @Mr.Scienceman2000 never recommend a change of product key when troubleshooting activation issues, as it can cause problems for determining cause.

Times out for me.

I still have CRT TVs in my house.

Going through the email archives it seems I can come up with some sort of response. BUT remember that my experience is in manufacturing and not necessarily in real world regarding this, And also, this is from a long time ago and someone may have come up with some new tricks. Of course there isn't a blanked "Windows 7 doesn't work on NVME" as there are examples of it working, even in my own experience. It isn't a cut and dry situation, as there are many factors involved: - whether UEFI is enabled or not - whether the M2 socket runs on SATA or PCIe lanes, or whether the board uses separate controllers for modes like AHCI, RAID or if it detects an NVME or NVME capabilities. - the NVME itself may not support booting an OS or the board may not allow booting an OS on NVME And all of the above includes the various firmware settings, ones you can set, ones that are locked, firmware versions, controller capabilities, board capabilities using UEFI/MBR options. When I started testing Win7 on NVME it was 2016. The typical issue we'd see was getting an 0x7B bugcheck and adding the storage drivers didn't fix it. I had seen issues where a Samsung NVME would boot an OS (Windows 8.1 and 10) on certain boards but not be bootable on other boards. Never got Windows 7 to boot on a Samsung NVME. Was able to get Windows 7 to boot on an Intel NVME on some boards but not all. Also, performance issues were observed on this Intel testing. Other instances where Windows 7 on Intel NVME would hard lock at POST. So for the production environment (which trickles down to personal preference) was to use NVME on Windows 7 only as storage drive, and only use M2 SATA for booting the OS. With the large amount of things that are involved with whether it will work or not is why I decided to not bother with it at all. Of course, those who want to run experiments certainly can, but be aware you may well run into the roadblocks that are present in the board or NVME firmware that you likely won't be able to change.

Systems with standard cases (desktop, pedestal, rack) get cleaned out fairly regularly. Perhaps only because something needs to get upgraded or replaced such as fans. Don't forget about notebooks! Those are my worst offenders for sure.

The Explorer shell is the thing everyone has a problem with. Alternate shells would solve the issues.

The first piece of potential incompatibility I see in the specs is the presence of an NVMe.

So far in my experience, Windows 11 is way worse than Windows 10. Mostly from a usability standpoint. While I have changed to Windows 10 on 2 computers now, I don't see myself changing to Windows 11 unless they fix some issues. First of all, 100% of my Win11 experience so far has been in offline or segregated networks. The UX is extremely slow and some portions do not even work. For example if I were to open an Explorer window (in any way you can think of doing it, like putting c: in the run box, doesn't matter) it will open a blank white window for about 3-4 minutes before it actually will show you the contents of the thing you are looking at. Be is c: or Libraries, doesn't seem to matter. I've considered running a trace on explorer to see what it is trying to do.

Done

Many times, the compatibility or requirements text on a peripheral speaks directly to any particular software that the vendor has for the device, either packaged with it or from their website. And the OSes listed also tie directly to their support policy. As we know, not supported doesn't mean it doesn't work.

This forum is English only. Edit your post to translate to English. I have already renamed the topic title.

Now will be the time to revisit and validate any archiving that needs to be done.

Not sure where this topic was supposed to go (it was posted into GD), if it is wrong, we can move it again later.