Hithere - I have an OfficeJet Pro 8610 that has worked perfectly for a million years. Recently I "upgraded" to windows 11....which i didn't like, so i downgraded back to Windows 10. At that point, my trusty printer stopped working. I've tried restarting everything. I tried uninstalling, and installing. I tried running the HP doctor; which initially found an error that was 'corrected'....but then could not print a test page. The Doctor suggested then printing an "internal test page" which WORKED....so there is some sort of connection between PC and printer........but then it said it could do no further fixes, and that I should try uninstalling and installing. Which I'd already done. I called HP to get help - and they said it was too old and could not help me. Anyone out there have the same problem that they could offer any suggestions?
Hi Kumar, and sorry for the delay. I didn't get notified of a reply...and thought my question was just sitting out there in the ether. I did the steps you suggested, and neither worked. Most recently, with adding the printer using the IP address....it finds the printer and allows it to be added, but then the "test page" does not print (nor does any other sample page i try to print). I've tried the HP Print and Scan Doctor as well. That gave me "Everything checks out okay with your product. If you would like to print a test page..." Of course, that didn't work either. It then suggested printing an "internal test page" which DID WORK...and then the Scan Doctor froze.
Just to restate how this started: i "upgraded" to windows 11 and then downgraded back (later that day ) to Windows 10...and printing no longer worked from this device. Still works without issue from our Mac and our phones. I'm sure there is some remnant of the Windows 11 "upgrade" somewhere in my system that is preventing it from working?
Unfortunately....nothing yet. HP won't help me because my printer is "too old". My HP printer works perfectly with our iphones, ipads and macbook.....it is just the HP Computer that it won't work with after the windows upgrade/downgrade. Frustrating.
I have an OfficeJet 4655 that no longer prints from an HP AIO after it was rolled back to W10 from W11. Tried everything including 2 hours on phone and remote connect with HP support. Printer works fine from iPhone. Going to try spc /scannow and if this doesn't work then do a W10 reinstall. Printer appears to be installed, can see cartridge levels, etc., with HP Smart app, but it will not print from an app like Word. Tried wired and wireless connection.
We have a shared internal dev environment and one dev was working on a feature branch with updated episerver nugets and when they ran their project locally and connected to the shared episerver database, it updated the database version from 7059 to 7060 (unfortunately the setting to automatically do these updates was turned on). Now we cannot run the project on that database version without updating the nugets sufficiently. An update to episerver is not going to be deployed soon to this project so we're left with trying to figure out how to solve this mess.
I'm afraid, to the best of my knowledge, there's no downgrade option so your best bet would be to roll back the database (if possible). You mentioned there's no recent backups but, depending on how your database is configured, you may still be able to roll back to a point in time. Rolling back an azure SQL database to a point in time should be pretty straightforward if you're using that. If you're using SQL server, it's not quite as straightforward but should still be possible (depending on your database recovery model). As I recall, the process involves a tail-log backup (which contains the transactions since the last backup), allowing the transactions to be replayed up to a point just before the database version was updated. I can't remember the exact process but I'm sure Google would be able to help.
I'd strongly advise against the suggestion of manually changing the database version in `sp_DatabaseVersion`. That may remove the initialisation error but basically all you're doing is masking the cause of that error. The database schema will still not match the codebase and so you'll most likely end up with many more, much harder to find errors cropping up throughout your solution. It may also cause you problems when you subsequently try to upgrade as the schema won't match the expected schema from in the database upgrade scripts.
Thank you for the helpful comments. I will have a look at using SQL Server transaction logs to bring an older backup up to speed, and at the very least configure a maintenance plan for frequent backups for the SQL server. It'd also probably be a good idea to have automatic database updates off for Episerver in the shared developer environment, like Tomas points out at the end of his blog.
I received my new watch after replacing my previous because 4.10 botched everything for me. I turned off Updates and guess what. Absolutely everything is working like a dream. OHR is great. in water pool swim HR and lap counting is dead on. NO skips in my music with my AirPods, and my phone reconnects every time I get near it, like it should.
A firmware update to official 4.10 botched up a watch such that you needed to replace the watch itself? I've heard of people in the beta streams getting mixed up, but even though, when connected to a pc they end up putting known/good firmware back on.
glad the new watch is working
I'll take your word for it. I dont change firmware on watch, but changed them on countless other things. firmware is firmware, usually. Its just a matter about getting into the correct bootstrap and loading whats needed. Garmin might make it complex to do that, I dunno
The problem with never updating is that you may find that eventually you can't use certain CIQ apps or data fields or watch faces. Or you may have trouble syncing with Connect. And you won't ever get any cool new features.
thanks for continuing to be interested in my problem. I appreciate it! I have a blueprint that was using color temperature in mireds to change color temperature using my lohas bulbs connected through ESPHome and Ikea 5 button switches to turn lights on and off, dim / brightness and warm / cool color temp.
first troubleshooting I did was to try to call service color temp when it stopped working. the rest of the functions work so RGBW color picker, on / off and dimming are still working. I lost color temp, I think after the 221.5.0 update.
My app is working as expected in the simulator on iOS 12.1, but not on my iOS 11.x device, and it is just a layout issue. I'm not aware of any major changes in layout constraints from 11 to 12, so I'm perplexed... I upgraded an older device from iOS 10 to 12 and my app layout works on it, so it seems something changed between iOS 11 and 12 regarding layout, but I don't know what that is...
How can I get a simulator running iOS 11.x to debug? I'll start debugging on my actual 11.x device, but I would also like to know how to get a simulator running older iOS versions? xcodebuild -showsdks says I only have 12.1 iphone/simulator 12.1 -- how do I run 11.x in the simulator, or older iOS versions in general in the simulator?
Same as guy above, XCode 15 and it only lists 17.0 in the simulator. If I look inside the xcode folders it lists lots of other ios versions, interestingly it doesn't actually list 17, just 8->16.4. How is it this fiddly and wierd to just get a simulator for different versions of ios!? I followed a few guides of downloading other versions of the simulators from github and something else with some commands, don't seem to make any diff, I don't see anything other than ios 17.0.
Hi, so me and my partner would like to make our agency using upwork and we saw that we would need Agency Plus to add members to the agency. I read from another post that if you downgrade to a basic Agency from Agency Plus, your members would get kicked out, is that correct? And another question I have is, would the history in the agency be gone when we move to Agency Plus? As in, would the kicked member track record in working in the agency be removed? And would we still have to continue paying for Agency Plus each month although we do not take any job at all during a particular month?Thank you.
Since having the Agency Plus plan is a requirement for being able to have additional members in your agency, if you ever decide to downgrade down the line, the members will no longer be part of the agency. However, you won't lose your work history, as contracts where a freelancer was hired under the agency will show both on their freelancer and their agency profiles. You can check this help article to learn more.
I am having the same issues. My WF-7720 is stuck in recovery mode. When I try to downgrade the firmware there's a message on the screen that says ROM NOT WRITABLE and all the lights are flashing. If I unplug the printer and then power it back up it says RECOVERY MODE. I've everything like the OP. John I followed the steps and I'm still in the same boat, stuck in recovery mode. Please help, please, if I don't finish these jobs it will be the end for me.
Good day. You need to use free recovery firmware for this (first enable firmwares for recovery mode in the WICReset options from the mian menu) then you will see new list for your printer in the main interface, select recovery firmware for you model and follow instructions.
I have tried this but the WF-7720 is not in the recovery list. There has to be a solution for this. I can't believe that the chipless firmware is being sold for my model printer and not working correctly.
I have been using Squarespace for a while now and I have come accustom to its quirks and format. I have had a mostly fine experience with it. I have just recently started a new website for a client and decided to start in 7.1 thinking it would be an upgrade and have better longevity in support, etc. However, I have lost certain functionality and would really prefer to not have to use custom code to get back.
3a8082e126