Notifications were on and Clock was allowed. The PC was awake. The work-around I used was to set 'Clock'on a second PC that didn't have the problem. It has been fixed in the latest general Windows update.
I use the Clock App for things like meeting I need to go to, laundry ready (I live in a flat with a shared laundry room two floors below me) and when to take my meds. (I'm older than most of you ...)
A recent (yesterday?) update to the app seems to have stopped it working. I realised the time...
I knew I wanted to update to the most recent release, but Windows Update wasn't doing so. The "Installation Assistant" did the job, but I think "Windows Update" should have updated Windows.
I have just reinstalled Windows 11 Pro on an existing licensed system. The "Windows Update" settings tab says "Your version of Windows has reached the end of service." Is it possible to update it, or do I have to do another clean install?
Edit: the ISO I downloaded installed version 22H2.
The Windows 11 requirements page says that a CPU of at least 1 GHz and 2 cores is required. I have a system with a 3.7 GHz 4 core CPU which isn't accepted. Possibly because it's an AMD? The system passes the other tests.
Possible solutions:
1. Hack the registry. My understanding is that...
amd processor
compatibility
cpu compatibility
future-proofing
hardware upgrade
internet access
lan security
learning curve
operating system
primary system
registry
system requirements
tech solutions
ubuntu
unsupported cpu
user concerns
windows 10
windows 11
I have a Windows 11-Pro system that suffered RAM failure. I thought there was so much corruption that it would be better to re-install Windows. However the installer now says the System doesn't meet the requirements for Windows 11. Is MS withdrawing support for systems that were previously...
Good idea, but when I checked "DirectPlay" it was already enabled.
This is probably a temporary fix, but re-installing the video card driver, followed by:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
has worked.
I'm somewhat behind the times in games ...
Bugs aren't so bad if there is a known work-around. My concern now is if I'll have to re-install the good version of DirectX every time Windows decides to do a non-optional 'update'.
I've found a fix - I've installed the 2010 version of DirectX. This leaves unanswered the question of whether the latest version is buggy or a "Break AMD Graphics" version.
After the latest huge pile of Windows Updates I get this error message when I try to run a game that was previously working. I've re-installed DirectX and the driver for the graphics card - not change. Is it possible to roll back to a working version of DirectX?